This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.
Source for ticket #19
cc
changetime
2011-01-24 06:56:30
component
WG1 - Exceptions
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.
id
19
keywords
milestone
owner
alexshinn
priority
major
reporter
alexshinn
resolution
wontfix
severity
status
closed
summary
when to throw an error
time
2010-02-23 16:43:10
type
defect
Changes
Change at time 2011-01-24 06:56:30
author
cowan
field
comment
newvalue
WG1 voted for the R5RS status quo.
oldvalue
2
raw-time
1295823390000000
ticket
19
time
2011-01-24 06:56:30
Change at time 2011-01-24 06:56:30
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1295823390000000
ticket
19
time
2011-01-24 06:56:30
Change at time 2011-01-24 06:56:30
author
cowan
field
status
newvalue
closed
oldvalue
new
raw-time
1295823390000000
ticket
19
time
2011-01-24 06:56:30
Change at time 2010-03-16 06:18:04
author
kumoyuki
field
comment
newvalue
"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.
oldvalue
1
raw-time
1268695084000000
ticket
19
time
2010-03-16 06:18:04
Change at time 2010-03-16 06:18:04
author
kumoyuki
field
milestone
newvalue
oldvalue
raw-time
1268695084000000
ticket
19
time
2010-03-16 06:18:04