From ... From: Erik Naggum Subject: Re: Floating Point speed in Common Lisp Date: 1998/03/13 Message-ID: <3098801908586746@naggum.no>#1/1 X-Deja-AN: 333749059 References: <6e1v1c$7el@desire.lavielle.com> <4n1zw8j50i.fsf@rtp.ericsson.se> <87btvc8m8q.fsf@isttest.bogus> <4nwwe0gesm.fsf@rtp.ericsson.se> <87n2ev265j.fsf@isttest.bogus> <4nu393hj8t.fsf@rtp.ericsson.se> <87lnuf1yd6.fsf@isttest.bogus> <4npvjrh6g6.fsf@rtp.ericsson.se> <87iupj12zo.fsf@isttest.bogus> <35096D58.B149D0B5@computer.org> mail-copies-to: never Organization: Naggum Software; +47 8800 8879; http://www.naggum.no Newsgroups: comp.lang.lisp * Christopher J. Vogt | I forget if it was Steele or Gabriel who observed that one of the things | that makes programming in common lisp uniquely different from other | languages, is that to get good performance, you have to be intimately | familiar with your implementation. This sort of issue doesn't exist in | C, for example. One implementation of C is generally as fast (within a | factor of 2) as another. However, CL implementations can vary quite a | bit, in different areas. One might have (relatively) good FP performance | but horrible Bignum performance etc. I beg to differ. C systems (compilers, libraries, etc) generally differ by just as large factors as Common Lisp, often more, when non-trivial functions are used, and they tend to be for non-trivial programs, and optimizing C is generally very hard beyond the simple cases. I'm not saying that CL is doing a better job than C in the general case, but I'm getting somewhat peeved with the repetitive claims that C is so fast. it isn't. it never was. it's just that the language is fairly transparent down to the machine level so when you change something in the C code, you can predict the effect on the compiled machine code. that doesn't make it _fast_, it only ingratiates the control-freak aspect of most programmers. #:Erik -- God grant me serenity to accept the code I cannot change, courage to change the code I can, and wisdom to know the difference.