Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-han1.dfn.de!news-stu1.dfn.de!news.belwue.de!news.uni-stuttgart.de!news.urz.uni-heidelberg.de!not-for-mail
From: Nicolas Neuss <Nicolas.Ne...@iwr.uni-heidelberg.de>
Newsgroups: comp.lang.lisp
Subject: Re: Un-Great (Newbie) Expectations [was Re: Why is this code broken?]
Date: 13 Jun 2002 13:13:24 +0200
Organization: IWR
Lines: 13
Message-ID: <87ofef8m97.fsf@ortler.iwr.uni-heidelberg.de>
References: <advgm0$2gut6$1@ID-105510.news.dfncis.de> <2hvg8sskp6.fsf@vserver.cs.uit.no> <advkj7$2ij5g$1@ID-105510.news.dfncis.de> <QVIM8.19501$fT5.5090874@typhoon.ne.ipsvc.net> <ae0npr$2tebp$1@ID-105510.news.dfncis.de> <3D03EC84.933FCD7B@dls.net> <ae0rf7$2voth$1@ID-105510.news.dfncis.de> <3D03F3A5.E00083B4@dls.net> <ae0t5r$30tvb$1@ID-105510.news.dfncis.de> <3D040264.388E4A5C@dls.net> <gat-0906022007080001@192.168.1.50> <3D04963B.98307CB7@dls.net> <3D04C1F7.D20F5169@nyc.rr.com> <gat-1006021137540001@k-137- 79-50-101.jpl.nasa.gov> <873cvv3pr9.fsf@cs.uga.edu> <gat-1006021352550001@k-137-79-50-101.jpl.nasa.gov> <u0pN8.220551$xS2.16505491@news1.calgary.shaw.ca> <3232819785007234@naggum.net> <873cvtwjn7.fsf@noetbook.telent.net> <3232870303524784@naggum.net> <A7KN8.227827$xS2.16717864@news1.calgary.shaw.ca>
NNTP-Posting-Host: ortler.iwr.uni-heidelberg.de
X-Trace: news.urz.uni-heidelberg.de 1023966804 2823 129.206.120.136 (13 Jun 2002 11:13:24 GMT)
X-Complaints-To: usenet@news.urz.uni-heidelberg.de
NNTP-Posting-Date: 13 Jun 2002 11:13:24 GMT
X-Newsreader: Gnus v5.7/Emacs 20.7

"Geoff Summerhayes" <sNuOmSrPnA...@hNoOtSmPaAiMl.com> writes:

> But hard to avoid since interpreted code can be created at
> run-time, reducing the impact of a compile-only solution.
> Does anyone write Lisp code, compile it first, then test for
> correctness? For me testing almost always comes before compilation,
> unless the routine requires the additional speed to work.

In the CMUCL manual, compiled code is recommended even for debugging.
Also the additional checks during compilation are very useful for
finding bugs.

Nicolas.