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: quest for pass-by-reference semantics in CL References: <2h6627rlr0.fsf@vserver.cs.uit.no> <2hsn5araqe.fsf@vserver.cs.uit.no> <3229347076995853@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3229608336004164@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 15 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 May 2002 17:25:36 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1020619536 193.71.199.50 (Sun, 05 May 2002 19:25:36 MET DST) NNTP-Posting-Date: Sun, 05 May 2002 19:25:36 MET DST Xref: archiver1.google.com comp.lang.lisp:32903 * Erann Gat | Perhaps, but that still doesn't justify saying "It's call by value. | Period." At best, "It's call by value, and all the values are pointers | that are automatically dereferenced every time you refer to them." But | even that isn't entirely true because... Please listen. Call _by_ value is different from call _with_ value. The meaning of "value" is irrelevant. The fact that you cannot access the _binding_ of the value is the clue. In call _by_ reference, you do not pass _some_ references to objects, you pass references to _bindings_. -- 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.