Ticket #19 (closed defect: wontfix)

Opened 2 years ago

Last modified 16 months ago

when to throw an error

Reported by: alexshinn Owned by: alexshinn
Priority: major Milestone:
Component: WG1 - Exceptions Keywords:
Cc:

Description

R5RS defines many things as "is an error" without
any specification of what happens in that situation.
R6RS goes to the opposite extreme and specifies
as much as possible what exceptions are raised when.

Taking into account the system provided by ticket #18,
we need to come up with guidelines for when exceptions
should be raised, and clarify which R5RS "error" situations
should raise an exception or be left unspecified.

Change History

comment:1 Changed 2 years ago by kumoyuki

"Is an error" is fine for WG1. I see WG1 Scheme as vary much a "seat belts off" language. One's program shouldn't be doing things which create "is an error" situations anyway.

comment:2 Changed 16 months ago by cowan

  • Status changed from new to closed
  • Resolution set to wontfix

WG1 voted for the R5RS status quo.

Note: See TracTickets for help on using tickets.