From ... Path: archiver1.google.com!news1.google.com!news2.google.com!news.maxwell.syr.edu!uio.no!nntp.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Understanding #' and function variables Date: 03 Feb 2004 00:03:51 +0000 Organization: Naggum Software, Oslo, Norway Lines: 32 Message-ID: <2004-034-AZW-KL2065E@naggum.no> References: <20040201115211.GG8667@mapcar.org> <2004-032-742-KL2065E@naggum.no> <8MdTb.157308$sv6.871544@attbi_s52> <20040201211615.GI8667@mapcar.org> <2004-033-838-KL2065E@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: readme.uio.no 1075766631 19181 129.240.65.203 (3 Feb 2004 00:03:51 GMT) X-Complaints-To: abuse@uio.no NNTP-Posting-Date: Tue, 3 Feb 2004 00:03:51 +0000 (UTC) Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 Xref: archiver1.google.com comp.lang.lisp:11750 * Erik Naggum > There is no way in Common Lisp to refer to symbols in any but the > current thread. All references to values of symbols will therefore be > those in the current thread. * Erann Gat | Hogwash. | | ? (defvar *x* 1) | *X* | ? (defvar *p* (process-run-function "p" (lambda () (let ( (*x* 2) ) (loop))))) | *P* | ? *x* | 1 | ? (symbol-value-in-process '*x* *p*) | 2 | ? Hogwash? And PROCESS-RUN-FUNCTION and SYMBOL-VALUE-IN-PROCESS are specified /where/ in ANSI X3.226-1994? If you add extensions, it's your duty to maintain the semantics of the standard to which you purport to conform. If you fail in this duty, it is not the standard's fault. Upgrade your brain to acquire the concept of «context», please. -- Erik Naggum | Oslo, Norway 2004-034 Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.