From ...
Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!feed.news.tiscali.de!uio.no!nntp.uio.no!not-for-mail
From: Erik Naggum <erik@naggum.no>
Newsgroups: comp.lang.lisp
Subject: Re: Understanding #' and function variables
Date: 02 Feb 2004 22:54:38 +0000
Organization: Naggum Software, Oslo, Norway
Lines: 25
Message-ID: <2004-033-934-KL2065E@naggum.no>
References: <Sn1Tb.154045$5V2.806622@attbi_s53> <Vk3Tb.169001$4F2.20113811@twister.nyc.rr.com> <20040201115211.GG8667@mapcar.org> <OxaTb.170865$4F2.20209204@twister.nyc.rr.com> <fSbTb.156975$sv6.865734@attbi_s52> <2004-032-742-KL2065E@naggum.no> <8MdTb.157308$sv6.871544@attbi_s52> <20040201211615.GI8667@mapcar.org> <GAeTb.161070$nt4.733919@attbi_s51> <y8rmctl2.fsf@comcast.net> <RUfTb.158105$5V2.827517@attbi_s53> <znc18qbn.fsf@ccs.neu.edu> <gNOSPAMat-0202040845250001@k-137-79-50-101.jpl.nasa.gov> <wu75uzn9.fsf@ccs.neu.edu> <gNOSPAMat-0202041032030001@k-137-79-50-101.jpl.nasa.gov> <hdy9uuu0.fsf@ccs.neu.edu> <gNOSPAMat-0202041234580001@k-137-79-50-101.jpl.nasa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: readme.uio.no 1075762479 17305 129.240.65.203 (2 Feb 2004 22:54:39 GMT)
X-Complaints-To: abuse@uio.no
NNTP-Posting-Date: Mon, 2 Feb 2004 22:54:39 +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:11741

* Erann Gat
| Or are you really insisting that the Standard requires the language to
| be implemented in a way that fails when used with parallel processors?

  Another annoying straw man argument.

  The standard has specified the semantics of several operators, and
  that is the only interface you need to worry about.  If you start to
  worry about the implementation being in conflict with the standard,
  you are either a vendor or just plain nuts.  As a vendor, you would do
  whatever is necessary to remain conforming.  As just plain nuts, you
  would keep arguing that you cannot figure something out, so therefore
  there must be a flaw in reality.

  The function SYMBOL-VALUE is defined to return the value of the global
  binding of that symbol in the dynamic environment.  How it arranges
  for this is none of your business.  Whether there is a system-wide or
  a universe-wide global binding that you can modify or not is not part
  of the standardized interface.

-- 
Erik Naggum | Oslo, Norway                                      2004-033

Act from reason, and failure makes you rethink and study harder.
Act from faith, and failure makes you blame someone and push harder.