On 2012-10-26 00:03, Tyro[17] wrote:
Just got around to looking back at this. That was in fact the piece of
missing information. I never linked to or modified the dmd.conf file.
Every thing works great now. Thanks for the DMV info but I prefer to do
this manually. This way I'll never have to
On 2012-10-26 01:18, Sean Kelly wrote:
On Oct 25, 2012, at 4:12 PM, Alex Rønne Petersen a...@lycus.org wrote:
What's used on OS X? I forget...
The method used is similar to how GC works on Windows--there's a kernel call
that can be used to explicitly suspend a thread. I can't remember the
Joseph Rushton Wakeling:
Suppose I have some data in an 2-dimensional associative array
(it could be larger dimension, but let's limit it to 2d for
now). I'm using an associative array because the underlying
data is sparse, i.e. for any given index pair (i, j) there's
most likely not an
On 10/26/2012 04:51 AM, H. S. Teoh wrote:
Hmm. Try apt-get install libppl0.11-dev, maybe? That's where that file
should be. AFAIK apt-get build-dep should've pulled that one in, but
just in case it didn't, this may help.
It's installed, but the headers in /usr/include/x86_64-linux-gnu/ instead
Not sure if this is a bug or intended behavior:
import std.traits;
struct S {
int i;
T opCast(T)() if(isFloatingPoint!T) {
return cast(T)i;
}
}
template myIsFloatingPoint(T) {
enum myIsFloatingPoint = isFloatingPoint!T
|| __traits(compiles, {
On Thu, 25 Oct 2012 01:15:06 +0100, Joseph Rushton Wakeling
joseph.wakel...@webdrake.net wrote:
Hello all,
I've just been playing with dirEntries and by the looks of it, it
returns these entries in arbitrary order.
On windows, assuming it was using FindFirstFile or similar you would get
On Thursday, 25 October 2012 at 16:39:57 UTC, Dan wrote:
From bug tracker I see that Proxy has a few issues, so this has
likely been seen. But what would cause this error?
tmp/c.d(16): Error: overloads pure nothrow @safe double(auto
ref CcRate b) and pure nothrow @safe double(auto ref CcRate
On Friday, 26 October 2012 at 13:55:35 UTC, simendsjo wrote:
Not sure if this is a bug or intended behavior:
...
So.. What do I need to implement for a struct to be a valid
built-in type?
All valid properties (min, max etc) and operators for that type?
I am looking for something similar. I
On Friday, October 26, 2012 15:55:34 simendsjo wrote:
So.. What do I need to implement for a struct to be a valid
built-in type?
All valid properties (min, max etc) and operators for that type?
So, you want stuff like isFloatingPoint and isNumeric to return true for a
user-defined struct?
On Fri, Oct 26, 2012 at 02:36:18PM +0200, Joseph Rushton Wakeling wrote:
On 10/26/2012 04:51 AM, H. S. Teoh wrote:
Hmm. Try apt-get install libppl0.11-dev, maybe? That's where that
file should be. AFAIK apt-get build-dep should've pulled that one in,
but just in case it didn't, this may help.
Is there a way to get the current exception inside a scope(failure)? I
have a try..catch around my main loop which simply logs the caught
exception and rethrows it. I'd like to replace this with a simple scope
(failure) but I haven't found any way to access the exception causing the
On Thursday, 25 October 2012 at 15:05:05 UTC, Zhenya wrote:
Hi!
Tell me please,are any TypeInfo/typeid/classinfo manipulations
possible?
For example I need a struct that overload typeid, or something
like that?
Some time ago I tried to write some smart pointer that overlad
classinfo
On 10/26/2012 06:57 PM, H. S. Teoh wrote:
Hmm. Are the Ubuntu patches incomplete then? I would've thought the
patches in debian/patches should have taken care of this.
I've posted a follow-up to the d.gnu list, since that's really where this
discussion belongs, but just to say you were
To learn about shared attribute I've copied nearly verbatim an
example from Andreis book. The code:
import core.atomic;
struct Data{
int value;
}
shared struct SharedStack(T) {
private shared struct Node{
T data;
Node* next;
this(T value){data = value;};
}
private Node*
On Friday, October 26, 2012 19:53:04 Justin Whear wrote:
Is there a way to get the current exception inside a scope(failure)? I
have a try..catch around my main loop which simply logs the caught
exception and rethrows it. I'd like to replace this with a simple scope
(failure) but I haven't
On Fri, 26 Oct 2012 17:33:48 -0400, Jonathan M Davis wrote:
On Friday, October 26, 2012 19:53:04 Justin Whear wrote:
Is there a way to get the current exception inside a scope(failure)? I
have a try..catch around my main loop which simply logs the caught
exception and rethrows it. I'd like to
On Friday, October 26, 2012 21:37:00 Justin Whear wrote:
My understanding is that scope(failure) simply lowers to the catch block
of a try..catch, so there's no implementation obstacle to making the
exception available. Are there known syntax or correctness obstacles to
allowing something like
On Friday, 26 October 2012 at 15:14:56 UTC, Dan wrote:
Still trying to understand this. I found that if I change the
following in Proxy it this example (r1 + r2) works fine. Plus
the unit tests that are there still work. But, honestly I don't
understand why...yet.
Thanks,
Dan
- From
On 27-10-2012 01:03, Minas wrote:
So the delete keyword has been deprecated - so good bye manual memory
management...
Um, no. Use destroy() from the object module instead. To free memory
from the GC, use core.memory.GC.free().
I have read in some threads that delete is an unsafe
On Sat, Oct 27, 2012 at 01:03:14AM +0200, Minas wrote:
So the delete keyword has been deprecated - so good bye manual
memory management...
Um, that's a misconception. If you want manual memory management, use
malloc(), free(), and emplace.
I have read in some threads that delete is an unsafe
On Friday, October 26, 2012 16:12:15 H. S. Teoh wrote:
The problem is that you can call delete on GC'd objects, which in some
cases causes bad interaction with the GC. That's why it has been
deprecated.
The intention was never to get rid of manual memory management. It was
to prevent unsafe
On Saturday, October 27, 2012 01:09:39 Alex Rønne Petersen wrote:
On 27-10-2012 01:03, Minas wrote:
So the delete keyword has been deprecated - so good bye manual memory
management...
Um, no. Use destroy() from the object module instead.
Definitely, though it's important to note that what
22 matches
Mail list logo
