From: Erik Naggum <>
Date: 05 Sep 2002 13:17:33 +0000
Newsgroups: comp.lang.lisp
Message-ID: <>

* 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.