Re: Template constraint error.

2013-10-10 Thread Johannes Pfau
Am Thu, 10 Oct 2013 16:46:18 +0200 schrieb "Gary Willoughby" : > class Foo(T) : Bar!(int) if (is(T == string)) // <-- > template constraint causes error. This syntax was added in a more recent frontend release. You should do this instead for older frontend versions: --- class Foo(T)

Re: Error: undefined identifier executeShell

2013-10-10 Thread Dicebot
On Thursday, 10 October 2013 at 15:17:55 UTC, Iain Buclaw wrote: pragma(msg, __VERSION__); Yeah, I mean without creating temporary file and compiling it ;) Not really big deal, but sounds quite trivial and will simplify some tooling.

Re: Error: undefined identifier executeShell

2013-10-10 Thread Iain Buclaw
On 10 October 2013 16:13, Dicebot wrote: > On Thursday, 10 October 2013 at 14:59:05 UTC, Iain Buclaw wrote: >> >> ... > > > That reminds me - is there a gdc flag that makes it print used D front-end > version? pragma(msg, __VERSION__); -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';

Re: Error: undefined identifier executeShell

2013-10-10 Thread Dicebot
On Thursday, 10 October 2013 at 14:59:05 UTC, Iain Buclaw wrote: ... That reminds me - is there a gdc flag that makes it print used D front-end version?

Re: Error: undefined identifier executeShell

2013-10-10 Thread Iain Buclaw
On 10 October 2013 15:31, Gary Willoughby wrote: > Using Debian7, gcc-4.8, gdc-4.8 from the `testing main` debian source. > > import std.stdio; > import std.process; > > void main() > { > string x = executeShell("uname").output; > wri

Template constraint error.

2013-10-10 Thread Gary Willoughby
Using Debian7, gcc-4.8, gdc-4.8 from the `testing main` debian source. import std.stdio; class Bar(T) if (is(T == int)) { this() { writefln(T.stringof); } } class Foo(T) : Bar!(int)

Error: undefined identifier executeShell

2013-10-10 Thread Gary Willoughby
Using Debian7, gcc-4.8, gdc-4.8 from the `testing main` debian source. import std.stdio; import std.process; void main() { string x = executeShell("uname").output; writefln(x); } $ gdc test.d -o test test.d:6: Error: unde

Re: gdb halts on non-errors

2013-10-10 Thread Iain Buclaw
On 10 October 2013 05:15, "Øivind" wrote: > Hi, > Debugging issues with GDB currently a bit of a pain because it halts on > several different non-errors. Could you advise on how to get around this. > Examples on places it will halt are below. The first ones are actually Vibe > specific, but the la