Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!212.177.105.133!news.mailgate.org!news-out.tin.it!news-in.tin.it!news1.tin.it.POSTED!not-for-mail
From: "Pierpaolo BERNARDI" <pierpaolo_berna...@hotmail.com>
Newsgroups: comp.lang.lisp
References: <3D8C8C43.819731FF@eurocom.od.ua> <3F9j9.145684$pX1.5222736@news2.tin.it> <ammdk3$2fk$1@usenet.otenet.gr> <UUBj9.129680$ub2.2819154@news1.tin.it> <ammrr2$gaq$1@usenet.otenet.gr> <qvCj9.129983$ub2.2823632@news1.tin.it> <amn0dh$k9k$1@usenet.otenet.gr>
Subject: Re: read-right-paren
Lines: 33
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Message-ID: <CeFj9.131020$ub2.2843683@news1.tin.it>
Date: Mon, 23 Sep 2002 14:07:30 GMT
NNTP-Posting-Host: 80.104.243.121
X-Complaints-To: newsmaster@tin.it
X-Trace: news1.tin.it 1032790050 80.104.243.121 (Mon, 23 Sep 2002 16:07:30 MET DST)
NNTP-Posting-Date: Mon, 23 Sep 2002 16:07:30 MET DST
Organization: TIN


"ilias" <at_n...@pontos.net> ha scritto nel messaggio news:amn0dh$k9k$1@usenet.otenet.gr...

> >>>>>Usually, #\) has a reader macro associated to it that just signals
> >>>>>an error with a message of "close paren found at top level".
> >>>>this is not true for an ANSI Conforming Common Lisp immplementation:
> >>>Uh?  The CL spec says #\) is invalid, so a conforming implementation 
> >>>can do whatever it likes.

I was wrong on this. The spec mandates that an error must be signaled.

> >>see below.
> > What?
> link

> the crap comes from the online version of the ANSI Common Lisp specs.
> replace simply *right-parenthesis* with *macro-character*, then you have 
>   original text.

If you change pieces at random, then it is not the standard.

You say:

>>>>" A *right-parenthesis* has an associated function called a reader macro
>>>>function that implements its specialized parsing behavior. [...] "

The "specialized parsing behavior" of ) is mandated by the 
standard to be the signaling of an error of type READER-ERROR.
See 2.4.2 and 2.1.4.3


P.