From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!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 10:56:11 +0000 Organization: Naggum Software, Oslo, Norway Lines: 18 Message-ID: <3240212171035953@naggum.no> References: <3240164830618395@naggum.no> <3240206449214856@naggum.no> <3240210721844260@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: maud.ifi.uio.no 1031223371 1557 129.240.64.16 (5 Sep 2002 10:56:11 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 5 Sep 2002 10:56:11 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:39694 * Tim Bradshaw | I think that you are assuming that I'm doing this the proper way - namely by | reading tokens and looking at what they are. But I'm not, I'm trying to | glue something together out of READ and bits of string. But this must necessarily fail. You cannot possibly make this work. | I realise that this is not the right way to do what I'm trying to do, but I | wanted to see if I could do it without either implementing a token reader | from the spec, or finding the system's one. I really thought this was obvious from the outset: It cannot be done. -- 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.