From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed1.bredband.com!bredband!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Idiot's guide to special variables take 2 Date: 18 Nov 2002 18:19:14 +0000 Organization: Naggum Software, Oslo, Norway Lines: 19 Message-ID: <3246632354249421@naggum.no> References: <3246463395155052@naggum.no> <87k7jcautp.fsf@darkstar.cartan> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1037643554 17462 129.240.65.5 (18 Nov 2002 18:19:14 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 18 Nov 2002 18:19:14 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:47085 * Rob Warnock | Well, it *can*, of course, access any new lexical bindings introduced in | the expression being EVAL'd, as well as any lexical bindings previously | closed over by functions called by the EVAL'd code. You didn't really | mean to exclude those when you said "/no/ lexical ones", did you? I fail to grasp what the problem is. The function `eval´ is no different from any other function. That is the key. No other function can access the caller's lexical environment, either. WTF is so special about `eval´ that it needs all this bogus attention? Yes, you call a function that has captured some lexical bindings, but that does not change the fact that function /calls/ in Common Lisp do not, cannot, know anything about the caller's lexical environment. -- 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.