From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!skynet.be!skynet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Removing an item from a list? References: <3CBF0E57.A51F1E60@hongkong.com> <7rMv8.12537$N16.497952@news1.calgary.shaw.ca> <87vgao9o94.fsf@Astalo.y2000.kon.iki.fi> Mail-Copies-To: never From: Erik Naggum Message-ID: <3228226051139456@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Apr 2002 17:27:31 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1019237251 193.71.199.50 (Fri, 19 Apr 2002 19:27:31 MET DST) NNTP-Posting-Date: Fri, 19 Apr 2002 19:27:31 MET DST Xref: archiver1.google.com comp.lang.lisp:32028 * Kalle Olavi Niemitalo | Is REMOVE-IF TEST SEQUENCE :COUNT NIL guaranteed to give | elements to TEST in the same order as they are in SEQUENCE? | I don't see why an implementation would do otherwise, though. I think this case is fairly obvious (i.e., I would complain if anyone were "smart" and did something else), but it is less obvious that supplying :from-end t :count nil will call the test on elements in the reverse order, since from-end is specified to have an effect only when count is non-nil. All implementations that I can test this on, however, do call test in the reverse order. [I used this simple call to see the effect: (remove-if #'print '(1 2 3 4) :from-end t).] /// -- 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. Post with compassion: http://home.chello.no/~xyzzy/kitten.jpg