I am guessing I will need to raise issues in the various issue trackers but:

I am finding that GtkD highlights some issues for GDC and LDC2. One of the moment relates to gtk.Builder.connectSignals. My code compiles and runs as expected with DMD, but with GDC and LDC2 the signals fail to connect.

Also interesting to note that -o- appears to do bizarre things with both DMD and LDC2 (not an issue for GDC of course).

-- 
Russel.
==============================================================================
Dr Russel Winder       Director
It'z Interactive Ltd   t: +44 20 7585 2200        voip: sip:russel.winder@ekiga.net
41 Buckmaster Road     m: +44 7770 465 077        xmpp: russel@winder.org.uk
London SW11 1EN, UK    w: www.itzinteractive.com  skype: russel_winder

On 12/22/2013 11:46 PM, Russel Winder wrote:
> Also interesting to note that -o- appears to do bizarre things with both
> DMD and LDC2 (not an issue for GDC of course).

What are you expecting -o- to do? It is documented to suppress generation of .o files.

http://digitalmars.com/d/1.0/dmd-linux.html

On 23 December 2013 10:03, Walter Bright <newshound2@digitalmars.com> wrote:
> On 12/22/2013 11:46 PM, Russel Winder wrote:
>>
>> Also interesting to note that -o- appears to do bizarre things with both DMD and LDC2 (not an issue for GDC of course).
>
>
> What are you expecting -o- to do?

A better question would be 'In what context are you using -o-?'  As it might not be in regards to the compiler at all.

On 23 December 2013 10:51, Iain Buclaw <ibuclaw@gdcproject.org> wrote:
> On 23 December 2013 10:03, Walter Bright <newshound2@digitalmars.com> wrote:
>> On 12/22/2013 11:46 PM, Russel Winder wrote:
>>>
>>> Also interesting to note that -o- appears to do bizarre things with both DMD and LDC2 (not an issue for GDC of course).
>>
>>
>> What are you expecting -o- to do?
>
> A better question would be 'In what context are you using -o-?'  As it might not be in regards to the compiler at all.

As for GDC it could one of two things.

1) Write assembly output to stdout
2) Create an executable named -

On Mon, 2013-12-23 at 02:03 -0800, Walter Bright wrote:
> On 12/22/2013 11:46 PM, Russel Winder wrote:
> > Also interesting to note that -o- appears to do bizarre things with both DMD and LDC2 (not an issue for GDC of course).
> 
> What are you expecting -o- to do? It is documented to suppress generation of .o files.

The questions I have are:

Should -o- stop the creation of the final executable?

Why is a file with the name of the final executable created?

What I had inferred, perhaps erroneously, was that -o- would just avoid writing the .o files whilst creating the final executable. However neither DMD or LDC2 do this. LDC2 generates no files, whilst DMD generates a file with the name of the final executable but which is not an executable.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Mon, 2013-12-23 at 10:51 +0000, Iain Buclaw wrote:
[…]
> As for GDC it could one of two things.
> 
> 1) Write assembly output to stdout
> 2) Create an executable named -

Are either of those actually useful?

-o- is not something I would ever think of as an option to any GCC-based compiler, perhaps I am missing something :-)
-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On 23 December 2013 16:03, Russel Winder <russel@winder.org.uk> wrote:
> On Mon, 2013-12-23 at 10:51 +0000, Iain Buclaw wrote:
> […]
>> As for GDC it could one of two things.
>>
>> 1) Write assembly output to stdout
>> 2) Create an executable named -
>
> Are either of those actually useful?
>
> -o- is not something I would ever think of as an option to any GCC-based compiler, perhaps I am missing something :-)
> --

Yes, you are missing an optional space between the o and the -. ;)

On Monday, 23 December 2013 at 16:04:00 UTC, Russel Winder wrote:
> -o- is not something I would ever think of as an option to any GCC-based
> compiler, perhaps I am missing something :-)

Isn't this option borrowed from gcc?

On Tue, 2013-12-24 at 10:27 +0000, Kagamin wrote:
> On Monday, 23 December 2013 at 16:04:00 UTC, Russel Winder wrote:
> > -o- is not something I would ever think of as an option to any
> > GCC-based
> > compiler, perhaps I am missing something :-)
> 
> Isn't this option borrowed from gcc?

I think that is the whole point, whatever dmd and ldc2 do as command line options, gdc is a part of GCC and so follows the gcc, g++, etc. command line options.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder