From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!195.54.122.107!newsfeed1.bredband.com!bredband!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: When to recompile/reeval? Date: 15 Oct 2002 14:47:28 +0000 Organization: Naggum Software, Oslo, Norway Lines: 45 Message-ID: <3243682048034314@naggum.no> References: <3da46228.129380253@netnews.attbi.com> <3243592697125968@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1034693249 14210 129.240.65.5 (15 Oct 2002 14:47:29 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 15 Oct 2002 14:47:29 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:43937 * Peter Seibel | Does that work even in implementations that don't make much of a | distinction between compiled and interpreted code. For example, I've been | using SBCL and was reading something about it the other day that said | (paraphrasing from memory) that they barely have an interpreter and | pretty much compile everything all the time. You would have to find out if SBCL expands macros too early even when you want to run interpreted. In my view, that is a serious disservice to its programmers, when the value of actually working with interpreted code is so obvious when you actually need it. Performance is the key, but Common Lisp has generally been willing to consider programmer performance as a higher value than code performance in some stages of development. | [Goes to browse through the HyperSpec]. :) | Okay, I see "3.2.2.3 Semantic Constraints" talking about the things that | you can count on being the *same* between compiled and interpreted | evaluation; is there somewhere else that talks about required | *differences*. Are there any? I expect to be able to change a macro definition and its interpreted users will reflect the chang while its compiled users would not. (defmacro macro-expansion-test () (print "I'm being expanded!") `(print "I'm the expansion!")) (defun expanded-when () (macro-expansion-test)) Evaluate these and see what `(expanded-when)´ produces when you evaluate it twice in a row. If you get the first `print´ while defining it, your environment is very eager. If you get the first `print´ only once, it does the expansion on the first evaluation. I expect it on both. Then `(compile 'expanded-when)´ and it should print "I'm being expanded!" and calling it should only produce "I'm the expansion". -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.