From ...
Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!howland.erols.net!news-feed.ifi.uio.no!ifi.uio.no!not-for-mail
From: Erik Naggum <erik@naggum.no>
Newsgroups: comp.lang.lisp
Subject: Re: READ-DELIMITED-FORM
Date: 05 Sep 2002 15:06:51 +0000
Organization: Naggum Software, Oslo, Norway
Lines: 15
Message-ID: <3240227211626185@naggum.no>
References: <ey3heh5etgb.fsf@cley.com> <ey37ki1ejg2.fsf@cley.com> <3240164830618395@naggum.no> <ey3it1kddt4.fsf@cley.com> <3240206449214856@naggum.no> <ey38z2gdaoo.fsf@cley.com> <3240210721844260@naggum.no> <ey3wuq0bts9.fsf@cley.com> <3240212171035953@naggum.no> <ey3d6rsbso2.fsf@cley.com> <ey3sn0oy579.fsf@cley.com> <3240220653549984@naggum.no> <ey3sn0oij31.fsf@cley.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: maud.ifi.uio.no 1031238411 2396 129.240.64.16 (5 Sep 2002 15:06:51 GMT)
X-Complaints-To: abuse@ifi.uio.no
NNTP-Posting-Date: 5 Sep 2002 15:06:51 GMT
Mail-Copies-To: never
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Xref: archiver1.google.com comp.lang.lisp:39746

* Tim Bradshaw
| It does?  I can find no mention of a case where READ returns zero values in
| the entry on it in the spec.  Do you mean that the reader macro function
| should return zero values?

  Yes, that was what I meant.  My bad.  But sadly, this goes to show my main
  point, that the support for using `read´ in its own (re)implementation is
  insufficient.  You need to get below the values returned by read to be able
  to capture the return value of reader macros.

-- 
Erik Naggum, Oslo, Norway

Act from reason, and failure makes you rethink and study harder.
Act from faith, and failure makes you blame someone and push harder.