Visual D Build + DMD Bugginess = Bad

[Rainer Schuetze]

I'll push the issue up the todo list. Maybe I'm not getting a lot of 
these errors because I have applied the dmd patches in the bug reports 
190 and 4753...


dsimcha wrote:
> == Quote from Rainer Schuetze (r.sagitario at gmx.de)'s article
>> Could it be related to any of these?
>> http://d.puremagic.com/issues/show_bug.cgi?id=190
>> http://d.puremagic.com/issues/show_bug.cgi?id=3979
> 
> Yep, these look like at least part of the problem.  Glad someone else has already
> reduced them to sane test cases so I don't have to.  Reducing compiler bugs that
> only seem to occur in non-trivial, multi-module projects to decent test cases is a
> huge PITA.
> 
> Anyhow, the project in question is a very messy codebase because it grew very
> organically.  It's basically a haphazard collection of research prototype
> algorithms for predicting gene expression from DNA sequence, and every time I
> think of a new idea, I tend to just put it wherever I can make it fit and almost
> never bother with non-trivial refactoring.  Therefore, there are cyclic imports
> **everywhere**.
> 
>> I have that option on my todo list, but didn't implement it so far
>> because I was not aware of any problems with compiling multiple files.
>> I don't know if this is really an option for a larger project, but what
>> you can do is select "Custom Build Tool" for all files in the "Common
>> Properties" setting of the project property dialog and enter your own
>> command line and output file. But be warned: you will not get any
>> automatic dependency detection.
>> As editing the settings for a lot of files might be very annoying, you
>> might want to set it for one file and then edit the project file with a
>> text editor to copy the settings to other files.
>> Rainer
> 
> Since build process automation is by far the biggest reason why I use an IDE
> instead of a plain old editor, I'd rather just stick with Code::Blocks for now.
> Could you please bump this up the todo list, given that building multiple files
> simultaneously is buggy in ways that probably aren't going to get fixed too soon?