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 #513
cc
changetime
2013-07-07 03:20:44
component
WG1 - Core
description
Aaron Hsu writes:
There are places in the standard where we have fundamentally introduced gratuitous incompatibility with the R6RS standard “just because it’s R6RS.” An example is the `error` procedure. Here, there was no reason not to diverge from R6RS’ behavior, especially given that the R6RS behavior is a more expressive, useful form.
id
513
keywords
milestone
owner
alexshinn
priority
major
reporter
cowan
resolution
wontfix
severity
status
closed
summary
Error should have been R6RS-compatible
time
2013-05-13 08:32:19
type
defect
Changes
Change at time 2013-07-07 03:20:44
author
cowan
field
comment
newvalue
The WG decided by unanimous consent to take no action on this ticket.
oldvalue
3
raw-time
1373142044410382
ticket
513
time
2013-07-07 03:20:44
Change at time 2013-07-07 03:20:44
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1373142044410382
ticket
513
time
2013-07-07 03:20:44
Change at time 2013-07-07 03:20:44
author
cowan
field
status
newvalue
closed
oldvalue
new
raw-time
1373142044410382
ticket
513
time
2013-07-07 03:20:44
Change at time 2013-05-13 08:33:39
author
cowan
field
comment
newvalue
R6RS in turn was gratuitously incompatible with SRFI 23, another extremely common SRFI (it is almost always presumed by reference implementations of other SRFIs, even those that predated it). The choice was R6RS, SRFI 23, or both (under different names), and any of these choices would have been justifiable. The WG went with SRFI 23.
oldvalue
2
raw-time
1368408819804128
ticket
513
time
2013-05-13 08:33:39
Change at time 2013-05-13 08:32:32
author
cowan
field
comment
newvalue
oldvalue
1
raw-time
1368408752484437
ticket
513
time
2013-05-13 08:32:32
Change at time 2013-05-13 08:32:32
author
cowan
field
description
newvalue
Aaron Hsu writes:
There are places in the standard where we have fundamentally introduced gratuitous incompatibility with the R6RS standard “just because it’s R6RS.” An example is the `error` procedure. Here, there was no reason not to diverge from R6RS’ behavior, especially given that the R6RS behavior is a more expressive, useful form.
oldvalue
Aaron Hsu writes:
There are places in the standard where we have fundamentally introduced gratuitous incompatibility with the R6RS standard “just because it’s R6RS.” An example is the error procedure. Here, there was no reason not to diverge from R6RS’ behavior, especially given that the R6RS behavior is a more expressive, useful form.
raw-time
1368408752484437
ticket
513
time
2013-05-13 08:32:32