[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: (BUG LISP) at MIT-MC
- Subject: Re: Errors
- From: EB@MIT-AI
- Date: Thu, 7 Nov 80 19:19:56 GMT
- Cc: JAR at MIT-MC Date: 10 JUL 1980 1940-EDT From: JAR at MIT-MC (Jonathan A. Rees) The reason for this is that ERROR was called with no interrupt channel argument while *RSET was (). That is a RUDE thing for ANY error detection code to do.
- Original-date: 07/11/80 15:19:56 EDT
Why? Seems controversial to me. If you don't want errors like that to
go immediately to top level, don't run with *RSET nil. Wouldn't
giving an interrupt channel argument typically make the error
correctable, while the whole point of using ERROR might be that a
semantically uncorrectable error has occurred? Also, note that errors
written as calls to FERROR will give no interrupt channel argument
(unless I am mistaken); does that mean that FERROR is a RUDE function
for ANY error detection code to call?