From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!129.240.148.23!uio.no!news-feed.ifi.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: READ-DELIMITED-FORM Date: 05 Sep 2002 13:17:33 +0000 Organization: Naggum Software, Oslo, Norway Lines: 29 Message-ID: <3240220653549984@naggum.no> References: <3240164830618395@naggum.no> <3240206449214856@naggum.no> <3240210721844260@naggum.no> <3240212171035953@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1031231853 2067 129.240.64.16 (5 Sep 2002 13:17:33 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 5 Sep 2002 13:17:33 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:39722 * Tim Bradshaw | Here's one thing that is very hard to do. Tim, this is a really good time for you go read the standard on the reader algorithm. I cannot fathom why you want to solve this any other way. | Consider the case where you are using string-and-glue R-D-F to read | conventional (...) syntax. Consider this: | | (x #+(or) dont:read) | | Immediately after reading x, you check for a closing delimiter. There | isn't one, so call READ again. Oops. What is the "oops" here? `read´ returns zero values in this case, and this is really standard behavior. The proposed #; reader maco would do precisely this, and end with `(values)´, and the code I posted here previously did. In fact, the standard ; reader macro scans until the end of the line and returns zero values. | So, to do it right you need to know what is coming next in much more detail. Sorry, this is still all wrong. -- 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.