| |
comp.lang.lisp |
>> Well, it's relative. Most of the other Lisp/Scheme implementations were > Which Lisps are you talking about? > So do many CL implementations on many benchmarks when "properly" I'd like to do another benchmark with an example from scientific computing --
> Jon Harrop <use...@jdh30.plus.com> writes:
>> Ulrich Hobelmann wrote:
>> > I wouldn't consider 5 times as slow as a *functional* language very
>> > competitive, but it might be fast enough for many problems.
>> two orders of magnitude slower. Stalin gets even closer than SBCL.
> is faster than this SBCL timing and it hadn't even been optimized yet.
> I would be surprised if Lispworks were much different in this regard
> as well.
>> any more...
> written. Several have been shown here in the past.
information on this but most of the sites I found were no longer up.
> starts with the original posting "showing" how bad CL is supposed to
> be when comparing optimized C/C++ with naively written CL. It also
> often ends with the CL version beating the optimized C/C++ version.
long ago where some Lisp gurus managed to code an equivalently-efficient
implementation in Lisp. However, it is important to know how easily an
efficient version can be written. LOC is a very rudimentary measure of
development time.
> tracing thing) don't have much of anything interesting to say about
> anything.
see modern functional language implementations doing so well at what is
arguably their weakest point.
next...
Dr Jon D Harrop, Flying Frog Consultancy
http://www.ffconsultancy.com