From: Ufasoft company
Subject: read-char, peek-char and recursive-p
Date: Sun, 11 Jan 2004 13:02:58 +0000
Message-ID: <49674185.0401110502.7d299eb6@posting.google.com>

If READ-CHAR don't signal error at end of file if eof-error-p=NIL, but
recursive-p=T, then what is meaning of this argument. It has no side
effects.

I assume read-char and peek-char must signal if recursive-p=T. It
clarified in PEEK-CHAR description, but READ_CHAR's don't say anything
about it

From: Christophe Rhodes
Subject: Re: read-char, peek-char and recursive-p
Date: Wed, 21 Jan 2004 15:38:18 +0000
Message-ID: <sqbroxs45x.fsf@lambda.dyndns.org>

······@ufasoft.com (Ufasoft company) writes:

> If READ-CHAR don't signal error at end of file if eof-error-p=NIL, but
> recursive-p=T, then what is meaning of this argument. It has no side
> effects.
>
> I assume read-char and peek-char must signal if recursive-p=T. It
> clarified in PEEK-CHAR description, but READ_CHAR's don't say anything
> about it

I'm not so sure.

At least the last time this discussion happened (see Message-ID
<··············@rtp.ericsson.se>), the consensus seemed to be that the
page for PEEK-CHAR was in error, or at least in apparent conflict with
CLHS 23.1.3.

I'm aware that Paul Dietz is testing this area, and that that might
have motivated your enquiry, Mr company; maybe other people could be
persuaded to offer insight?

Christophe
-- 
http://www-jcsu.jesus.cam.ac.uk/~csr21/       +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%")    (pprint #36rJesusCollegeCambridge)