I think D keeps improving. The gcc version is slower anyway, so I haven't bothered with it but my understanding is that they have made a lot of optimizations since we last discussed the performance of D on this group. Of course I haven't tested it out in a while.
I would use D exclusively for performance programming if it could get pretty close to C in speed. In principle the author of D claims it's has more potential than C does for optimizations. Are you using D now? - Don On Fri, 2007-06-15 at 14:45 -0400, Jason House wrote: > On 6/15/07, Phil G <[EMAIL PROTECTED]> wrote: > JIT didn't solve everything - the managed memory management in > Java (and C#) has overheard which JIT can not always optimized > away, for example. > > > The D programming language website argues in favor of garbage > collection... Even claiming that it could be faster than manual memory > allocation/deallocation. http://www.digitalmars.com/d/garbage.html > > > <venting> > I'm not yet sold on all the ideas... especially since D's GC crashes > when using the port to gcc. Arguments like "you don't have to debug > memory management code" (like on the website) are nice points, but > it's far more frustrating when the standard GC doesn't work. > </venting> > _______________________________________________ > computer-go mailing list > [email protected] > http://www.computer-go.org/mailman/listinfo/computer-go/ _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
