From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!colt.net!deine.net!hamster.europeonline.net!newsfeed.europeonline.net!nslave.kpnqwest.net!nloc1.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: setq setf References: <3224632704949565@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3224687455847318@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Mar 2002 18:30:46 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1015698646 193.71.199.50 (Sat, 09 Mar 2002 19:30:46 MET) NNTP-Posting-Date: Sat, 09 Mar 2002 19:30:46 MET Xref: archiver1.google.com comp.lang.lisp:28273 * Erik Naggum > You can always use setf where setq is applicable, so if you always use > setf, you cannot go wrong. setq only works on variables that are named > by symbols. * Paul Foley | And on symbol-macros, in which case it really means SETF. Yikes, it is true. Well, it should be, in order to make symbol-macros work transparently, but this should be a pretty good argument for always using setf, or even renaming setf to set. /// -- 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.