Newsgroups: comp.lang.lisp.x
Path: cantaloupe.srv.cs.cmu.edu!fs7.ece.cmu.edu!hudson.lm.com!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!news.sprintlink.net!unvax.union.edu!tardis.union.edu!kupermaj
From: kupermaj@tardis.union.edu (Joshua Kuperman)
Subject: Re: eof compatibility: xlisp & cl
Message-ID: <kupermaj.785215177@tardis.union.edu>
Sender: news@unvax.union.edu (System PRIVILEGED Account USENET News System)
Organization: Union College, Schenectady, NY
References: <3adr5o$qvu@mark.ucdavis.edu>
Distribution: inet
Date: Sat, 19 Nov 1994 03:19:37 GMT
Lines: 25

john@josquin.ucdavis.edu (John Gillespie) writes:



>(peek-char nil file-stream)

>(peek-char nil file-stream nil nil)

You are correct in noting that xlisp and common lisp do differ.  My
documentation for Xlisp plus 2.1f has a 2 argument function, while
CLtL2 has it defined as a 5 argument function.  It is sort of odd
since most of the xlisp functions do follow the
input-stream, eof-error-p, eof-value portion of the read instructions.

I'd suggest you redefine the instruction with a macro that checks what
system you're on, though hopefully otheres will have better solutions.
Or if you just want to use the one that's closer to common lisp you'll
have to go with clisp on this one.


--
Josh Kuperman                  
kupermaj@tardis.union.edu      


