From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!newsfeed.online.be!newsfeed.esat.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Help wiht LISP Function (Newbie) References: <26176b48.0110221114.7c6ba0c6@posting.google.com> <26176b48.0110231323.258670ae@posting.google.com> <3212998581648846@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3213009540532611@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Oct 2001 14:39:01 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader3.kpnqwest.net 1004020741 193.71.66.49 (Thu, 25 Oct 2001 16:39:01 MET DST) NNTP-Posting-Date: Thu, 25 Oct 2001 16:39:01 MET DST Xref: archiver1.google.com comp.lang.lisp:18594 * Kent M Pitman | Actually, for a function that takes an &REST argument, ESPECIALLY one that | takes a SINGLE &REST argument, it seems to me that APPLY should have been | defined to exceed CALL-ARGUMENTS-LIMIT since the list should just be directly | bindable to the rest variable. I don't see spreading it onto the stack and | then re-composing it to a list. This is only possible in a context where the compiler knows enough about the called function when it prepares the call to utilize this information. To make this generally available functionality would mean that apply would have to ask (the system about) the function whether it would like the arguments spread or not, but the function must also be prepared to accept individual arguments since that would be what a normal function call would have to provide, unless it went through a more expensive function call trampoline or something. /// -- Norway is now run by a priest from the fundamentalist Christian People's Party, the fifth largest party representing one eighth of the electorate. -- The purpose of computing is insight, not numbers. -- Richard Hamming