see also http://www.functionalfuture.com/d/
I remember poking around with the hashing example and the performance
improves when you preallocate the hash table. Otherwise the size of the
hash table is 10 slots and it isn't much of a hashing test. Other ways of
speeding it up is to use malloc instead of the GC but that is kindof
cheating.

I think this is a great idea but for some of the examples, it may be better to
wait until the DTL is available. Once the "standard library" can do basic data
types above the array level, the lines of code will go way down. The shootout
is not just about performance, but features. C++ does well because of the STL.
I think the contest sort of stipulates that only very-standard libraries can be
used. To be eligible, the DTL may need a "blessing" in the form of being
distributed with the compiler or something.
(This assumes the DTL does the sorts of things I'm expecting it to, ie container
classes, etc?)
Kevin

I think this is a great idea but for some of the examples, it may be better to
wait until the DTL is available. Once the "standard library" can do basic data
types above the array level, the lines of code will go way down. The shootout
is not just about performance, but features. C++ does well because of the STL.
I think the contest sort of stipulates that only very-standard libraries can be
used. To be eligible, the DTL may need a "blessing" in the form of being
distributed with the compiler or something.

It will be, as a peer of Phobos.

(This assumes the DTL does the sorts of things I'm expecting it to, ie

wait until the DTL is available.
I think the contest sort of stipulates that only very-standard libraries

used. To be eligible, the DTL may need a "blessing" in the form of being
distributed with the compiler or something.

But remember that http://www.digitalmars.com/d/index.html mentions:
"C++ implements things like resizable arrays and string concatenation as
part of the standard library, not as part of the core language. Not being
part of the core language has several suboptimal consequences."
as one of the motivations for D.
Regards,
Martin

The shootout is revived as a Debian Alioth project!
All interpreters and compilers updated to Debian unstable revisions. Anything
unavailable as a Debian package omitted from project. At this point that means
bigforth and mercury are not included."
D is not in Debian package form (why should it be)
maybe the Win32 shootout
http://dada.perl.it/shootout/