[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hmadorf on Lisp vs Fortran - declarations
- To: info-mcl%cambridge.apple.com%Riverside.SCRC.symbolics.com@Severn.SLTD.dialnet.symbolics.com
- Subject: Re: hmadorf on Lisp vs Fortran - declarations
- From: Peter Paine <firstname.lastname@example.org>
- Date: Thu, 29 Oct 1992 12:04-0000
- In-reply-to: <9210272249.AA16111@cambridge.apple.com>
Date: Tue, 27 Oct 1992 21:50-0000
From: email@example.com (David A. Moon)
> Date: Mon, 26 Oct 1992 16:19:05 -0500
> To: info-mcl
> From: firstname.lastname@example.org (by way of email@example.com (Andrew LM Shalit))
> ;; Conclusion: the declarations do not help in MCL 2.0f
I think you've been told this a few times before, but since
it was sent to info-mcl again I'll say it again, since
Integer declarations don't make any difference in most Common Lisps,
since integers have unlimited range. Try a fixnum declaration
if that's what you mean. Of course, you can't compute 200
factorial within the fixnum range, and you couldn't compute
it in Fortran either, since Fortran integers have about the
same limited range as Lisp fixnums. So I don't know
what you think this part of your benchmark proves; it doesn't
seem to have much to do with what you're trying to measure.
In black & white, the factorial 200 test spends most of it's time
allocating and processing bignums etc. It really does not test the sort
number crunching suitable for the normal work of "scientists, whose
experience is in numerical computing".
Yet again Lisp has shot itself in the foot. By allowing inexperienced
users the power to compute things that are out of the bounds of
possibility in most languages, Lisp gets bad marks for poor performance.
Many's the time that I have heard that Lisp is inappropriate for almost
anything other than academic exercises because it conses and garbage
collects! Ahhh... just because Lisp allows you to be dirty, does not
mean that you have to be. Many a major Lisp application runs with
negligable consing or GC.
So, to my point, why don't Lisps issue an automatic compiler warning
when declarations are being ignored.
I rejoice that this time the lecturer asked the experts what was going
on, rather than marching forward blind and damning Lisp with ever step.
Thank you Hans-Martin Adorf.