DMD front end should define a version containing the front end version

[H. S. Teoh]

On Sun, Feb 24, 2013 at 02:55:07PM -0800, Jonathan M Davis wrote:
> On Sunday, February 24, 2013 14:22:42 Walter Bright wrote:
> > On 2/24/2013 9:05 AM, Timon Gehr wrote:
> > > For the moment I'm just sticking with 2.060, because I have failed
> > > to reduce all the forward reference regressions introduced in
> > > 2.061.
> > 
> > I've found dustmite to be pretty helpful reducing things down.
> 
> I really need to figure out how to use dustmite one of these days. The
> last time that I tried to use it, I couldn't get it to work, but it
> may have been because rather than trying to find where the code
> stopped compiling, I was trying to find when the error message changed
> (the bug being encountered changed rather than a bug simply being
> introduced).
[...]

I started using dustmite a few days ago, and it's dead simple to use.
Just put your source code in some directory, say src, then construct a
command (or shell script) that returns exit status 0 if said code still
exhibits the problem you're trying to minimize, non-zero otherwise. Then
just run 'dustmite src $command', and it takes care of the rest.

Having said that, though, constructing the script can be a bit tricky,
depending on what bug you're trying to isolate. Like you said, simply
running dmd may not be enough (the compile error could have changed,
etc.). So you probably need to use grep -qF to grep for the exact error
message you're trying to isolate, and specifically test for that.


T

-- 
A program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes the potential for it to be applied to tasks that are
conceptually similar and, more important, to tasks that have not yet
been conceived. -- Michael B. Allen