Re: GDC doesn't catch this ambiguity

2014-01-11 Thread Mike
On Saturday, 11 January 2014 at 23:12:52 UTC, Mike wrote: On Saturday, 11 January 2014 at 12:39:59 UTC, Iain Buclaw wrote: On 11 January 2014 01:13, Mike wrote: GDC doesn't catch the ambiguity between... static nothrow pure void Write(A...)(A a) and static nothrow pure void Write(in str

Re: GDC doesn't catch this ambiguity

2014-01-11 Thread Mike
On Saturday, 11 January 2014 at 12:39:59 UTC, Iain Buclaw wrote: On 11 January 2014 01:13, Mike wrote: GDC doesn't catch the ambiguity between... static nothrow pure void Write(A...)(A a) and static nothrow pure void Write(in string text) ... but LDC does. Who's right? GDC is on 2

Re: GDC doesn't catch this ambiguity

2014-01-11 Thread sclytrack
On Saturday, 11 January 2014 at 12:39:59 UTC, Iain Buclaw wrote: On 11 January 2014 01:13, Mike wrote: LDC the LLVM D compiler (0.12.1): based on DMD v2.063.2 and LLVM 3.3 GDC arm-none-eabi-gdc (GCC) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. Also, is there a way to know which

Re: GDC doesn't catch this ambiguity

2014-01-11 Thread Iain Buclaw
On 11 January 2014 01:13, Mike wrote: > > LDC > the LLVM D compiler (0.12.1): > based on DMD v2.063.2 and LLVM 3.3 > > GDC > arm-none-eabi-gdc (GCC) 4.8.2 > Copyright (C) 2013 Free Software Foundation, Inc. > > Also, is there a way to know which version of DMD GDC is based on? GDC is on 2.064.2

Re: GDC doesn't catch this ambiguity

2014-01-10 Thread Mike
On Saturday, 11 January 2014 at 00:45:20 UTC, Mike wrote: In the following code: module trace; private nothrow pure void SendCommand(in int command, in void* message) { asm { "mov r0, %[cmd]; mov r1, %[msg]; bkpt #0xAB" : : [cmd] "r" command, [m