Ary Borenszweig wrote:
> Matti Niemenmaa escribió:
>> Ideally Walter would release his pile of test cases.
> 
> Isn't that dstress? There's quite a lot of test code there...

I don't think they're the same.

Still, testing against DStress helps, of course.

-- 
E-mail address: matti.niemenmaa+news, domain is iki (DOT) fi

Frank Benoit wrote:
> For the DWT library this would lead to compile times >15 minutes!
> 

I just tried building dwt-win with and without oneatatime enabled. Compiler options are '-O -release -inline'.  My PC is a 1.3 GHz athlon, with 896 MB RAM and a fairly fast HD.  I could have left out -inline, but the time savings likely wouldn't be significant.

Results:
all at once:    2 mins 27 secs, 5.9MB .lib file
one at a time:  39 minutes, 17 MB .lib file

I only did this once, but I expect the results would be about the same each time.  This is pretty ugly.

dwt-win is 6.9 MB of code in 353 files, about the same size as Tango.

torhu schrieb:
> dwt-win is 6.9 MB of code in 353 files, about the same size as Tango.

In addition ...
This does not mean it should be equal compile time. dwt uses tango, so its about double size of types/declarations for the compiler. So i wonder how it grows if you build an application on top of dwt with another 300 files :)

I gave it a try to measure both times for linux to compile dwt
dmd options: -g -gc -debug -v
dsss options: -full -v
2.8Ghz 2GB Ram

oneatatime=off :  0:31
oneatatime=on  : 31:49

I would reason, with oneatatime=off we see here a much stronger effect of more RAM size and CPU speed. With oneatatime=on the file I/O has much more weigth, so here the difference is not so big.

Frank Benoit schrieb:
> Gregor once explained why build tools need to call DMD once per file:
> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=57473 
> 
> 
> This makes dsss look like it is slow, but actually this is a concequence of a DMD workaround.
> 
> For the DWT library this would lead to compile times >15 minutes!
> 
> In the past I found the compile times always a big argument for D. Hopefully this point gets attention at digitalmars ;)

This bugzilla bug can happen if oneatatime is 'off'.
http://d.puremagic.com/issues/show_bug.cgi?id=1629

Using dsss with oneatatime=off and -full sometimes works around it.