Re: Defining SETF :AFTER methods in PCL

Article View: comp.lang.clos

Article #396

#396

From: John D. Burger
Date: Fri, 18 Jan 1991 22:27

18 lines
1049 bytes

desrivieres.parc@XEROX.COM (Jim des Rivieres) writes:

> Counterintuitively, all (setf xxx) functions and methods take the new
> value as their *first* argument;

What other argument position makes sense?  If you make it the last
argument of the SETF function/method, you can't have optional, rest or
keyword arguments.

John Burger

--
John Burger                                               john@mitre.org

"You ever think about .signature files? I mean, do we really need them?"
  - alt.andy.rooney

Technical Details

Message-ID: <1991Jan18.222754.24749@linus.mitre.org>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!linus!mingus!john

References: <91Jan17.101915pst.39425@nero.parc.xerox.com>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!linus!mingus!john
From: john@mingus.mitre.org (John D. Burger)
Newsgroups: comp.lang.clos
Subject: Re: Defining SETF :AFTER methods in PCL
Message-ID: <1991Jan18.222754.24749@linus.mitre.org>
Date: 18 Jan 91 22:27:54 GMT
References: <91Jan17.101915pst.39425@nero.parc.xerox.com>
Sender: john@mitre.clos
Distribution: inet
Organization: The MITRE Corporation, Bedford, MA 01730
Lines: 18
Nntp-Posting-Host: mingus.mitre.org

Reply to Parent Message