Ticket #17 (writing defect)
error
| Reported by: | alexshinn | Owned by: | arcfide |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | WG1 - Exceptions | Keywords: | |
| Cc: |
Description
Do we support the near ubiquitous SRFI-23 error procedure?
Change History
comment:2 Changed 2 years ago by arcfide
I'd say that we stick with the R6RS error function. It's more useful, and the SRFI-23 ERROR is trivial to implement in the R6RS ERROR function.
comment:3 Changed 19 months ago by cowan
- Status changed from new to closed
- Resolution set to fixed
The WG voted to accept SRFI-23 error.
comment:4 Changed 16 months ago by alexshinn
- Status changed from closed to reopened
- Resolution fixed deleted
Note: See
TracTickets for help on using
tickets.
Note that SRFI 23 error is incompatible with R6RS, because in R6RS the first argument is the object associated with the error (the "who"), whereas in SRFI 23 the first argument is the error string and all the rest are irritants.
We could have two procedures, error and error-on or the like.