Mono-D 0.3.9

[Marco Leise]

Am Fri, 11 May 2012 13:35:34 +0200
schrieb "alex" <info at alexanderbothe.com>:

> > Unfortunately there is no way to have the latest (alpha) 
> > MonoDevelop here at
> > work (because of company policy to use only stable software) , 
> > but will
> > definitely use 0.3.9 on Windows. BTW, any particular reason for 
> > using the
> > unstable MonoDevelop? :)
> 
> Not really, I just saw that the 2.6 version was the latest 
> available one for Linux on the MD Download page (that was in the 
> time before I knew that later versions are actually downloadable 
> though via console) and thought that this would be awkward... so 
> I decided to stick to the really latest version. Sounds a bit 
> confusing and not really reasonable but that's what I thought. -- 
> Except the 2.8 -> 2.9 upgrade problem I wasn't really 
> experiencing further bad effects by using the latest alpha/beta

At least, by the time 2.9 hits the repositories you have fixed all the bugs introduced by the transition! ;)
I'm still using the 2.8 compatible version, so things might have changed, but...
Can you make it easier to switch between compilers? I'd like to try building release versions with GDC for the optimizations and debug builds with DMD for the compilation speed. It could generally be useful to check if the code works on different compilers. The most painful part is that project specific compilation flags are not separate for each compiler. E.g. -funittest vs. -unittest.
Now a random thought from some make files: If there was a checkbox: "use compiler as linker", then you could define a "prefix for linker commands", so assuming the system default linker is used one could define linker flags for different compilers without worrying about -Wl or -L or -X,linker. That is definitely feasible on Linux, don't know about Windows where different linkers are in use.
Keep up the good work. No I'll have a look at what's going on in the DDT camp...

-- 
Marco