[dmd-internals] changeset 455

[Robert Clipsham]

On 28/04/10 22:45, Andrei Alexandrescu wrote:
> Ouch.

Ouch indeed.

> The problem is scale. Phobos is pretty large already. I did make changes
> in unittests as you suggest above, but there are a lot of those to make.
> Besides, when compiling Phobos as one unit and unittesting everything,
> all unittests are run in one shot so you don't know about modules and
> stuff.

This could be solved by named unit tests, or even getting druntime to 
output the name of the module before each test (although for projects 
with a lot of modules this could get spammy, as you've mentioned below).

> I improved that by painstakingly changing the build process to print and
> unittest one Phobos module at a time, while unittests are disabled in
> all other modules. That does help but is still far from perfect.

This is far from ideal, there should be a way to do this automatically, 
I agree.

> (Perfect: when it fails tell me where.)

What fails to tell you where?

> That would be too noisy.

I agree, it's far from ideal, there's not much of an option otherwise 
(as far as I can see) though without implementing a few thousand lines 
of code to handle a SIGSEGV or using a debugger though.

> Andrei