From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: (let ((..)) (eval '(arbitray expression))) References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3229898397566849@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 May 2002 01:59:57 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1020909597 193.71.199.50 (Thu, 09 May 2002 03:59:57 MET DST) NNTP-Posting-Date: Thu, 09 May 2002 03:59:57 MET DST Xref: archiver1.google.com comp.lang.lisp:33091 * D. Goel | PS: Several people wrote back explaining to me that elisp has dynamic | scoping and CL has lexical. Yeah, i understand that (atleast i think | i do.. some of it.. :-) even though i did confuse dynamic scoping ith | dynamic extent in a footnote). What i had wanted to do was to have | all my CL code, which was defined using lexical scope (and this can't | be changed) behave as if it had been declared using dynamic scope, as | far as the eval is concerned.. i guess that is too silly a demand.. No, it is not. The answer you seek is progv. I have replied to this three times, now. I guess the reason you do not respond to it is that you have to do some homework to value this answer. However, there is no point in explaining anything more to you until you go do your howework and learn what progv does. It takes time to explain, and the standard does it very well. If you have questions, they should be based on your understanding of its specification. -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief. 70 percent of American adults do not understand the scientific process.