[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Scheme-reports] file-error?, read-error?, and specificity of error objects
- To: scheme-reports <scheme-reports@x>
- Subject: [Scheme-reports] file-error?, read-error?, and specificity of error objects
- From: Andy Wingo <wingo@x>
- Date: Sat, 05 Jan 2013 20:03:16 +0100
Given the general lack of precision of error handling in the R7RS draft
-- something I am OK with -- the file-error? and read-error? predicates
seem out of place.
* They create an expectation of a well-specified error object
interface, where that is not really the case.
* They add verbiage to the report in unrelated sections. For example,
Section 1.3.2 ("Error situations and unspecified behavior") mentions
them specifically, while other kinds of errors are not mentioned.
My suggestion would be to remove all mention of "file-error?" and
"read-error?" from the report, and include in the larger report modules
which specify certain errors from those procedures.
As it is, I think most implementations will (define (file-error? x) #t),
which does no one any good.
Scheme-reports mailing list