Re: A CTFE Segfault (with explanation, but I'm not sure what the fix

2010-12-08 Thread Gareth Charnock
On 21/11/10 22:39, bearophile wrote: Gareth Charnock: struct LeafType { string Compile_not_ovloaded() { return "expression"; } }; Note that D structs don't require the ending semicolon, so in practice it is not used. And in D method names start with a lower ca

Re: A CTFE Segfault (with explanation, but I'm not sure what the fix

2010-11-22 Thread Per Ångström
On 2010-11-21 23:39, bearophile wrote: Gareth Charnock: string Compile_not_ovloaded() { return "expression"; } Note that [...] in D method names start with a lower case. Surely this must be more of a convention than a rule. Unless you are writing a standard

Re: A CTFE Segfault (with explanation, but I'm not sure what the fix

2010-11-21 Thread bearophile
Gareth Charnock: > struct LeafType { > string Compile_not_ovloaded() { > return "expression"; > } > }; Note that D structs don't require the ending semicolon, so in practice it is not used. And in D method names start with a lower case. Bye, bearophile

Re: A CTFE Segfault (with explanation, but I'm not sure what the fix is).

2010-11-21 Thread Gareth Charnock
Sorry, wrong mailing list. This should have gone to d.D

A CTFE Segfault (with explanation, but I'm not sure what the fix is).

2010-11-21 Thread Gareth Charnock
This code makes the DMD compiler segfault struct LeafType { string Compile_not_ovloaded() { return "expression"; } }; struct MatrixASTNode { LeafType Right; string Compile() { return Right.Compile_not_ovloaded(); } }; voi