[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: KMP@symbolics.com
- Subject: Issue: READ-DELIMITED-LIST-EOF
- From: masinter.pa@Xerox.COM
- Date: 9 Apr 89 23:31 PDT
- Cc: firstname.lastname@example.org
This is what I have filed under "READ-DELIMITED-LIST-EOF".
I think this could well be handled under ERROR-CHECKING-IN-IO-CHAPTERS or
----- Begin Forwarded Messages -----
Date: Mon, 28 Nov 88 17:17 EST
From: Barry Margolin <barmar@Think.COM>
Subject: EOF during READ-DELIMITED-LIST
According to CLtL p.378, "it is always an error to hit end-of-file
during the operation of READ-DELIMITED-LIST." This makes
READ-DELIMITED-LIST almost useless, because it means that some user
input to an application can cause undefined effects.
I think that this particular "is an error" was not intended this way.
READ-DELIMITED-LIST should be the function that the standard "(" macro
character uses, and the latter is defined to signal an error if an EOF
occurs before the matching delimiter is read. Also, the previous
sentence says that this is the reason that there is no EOF-ERROR-P
argument; the implication is that READ-DELIMITED-LIST has an implicit
EOF-ERROR-P argument that is always non-NIL.
Has this already been cleaned up?
----- Next Message -----
Date: 29 Nov 88 14:45 PST
Subject: Re: EOF during READ-DELIMITED-LIST
In-reply-to: Barry Margolin <barmar@Think.COM>'s message of Mon, 28 Nov 88
To: Barry Margolin <barmar@Think.COM>
As far as I know, there is no cleanup issue regarding READ-DELIMITED-LIST.
I think you might be proposing to change an "is an error" in CLtL into a
"signals an error"; if so, you might consider specifying the class of error
----- End Forwarded Messages -----