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 #17
cc
changetime
2012-10-04 23:55:47
component
WG1 - Exceptions
description
Do we support the near ubiquitous SRFI-23 error procedure?
id
17
keywords
milestone
owner
arcfide
priority
major
reporter
alexshinn
resolution
fixed
severity
status
closed
summary
error
time
2010-02-23 16:37:52
type
defect
Changes
Change at time 2012-10-04 23:55:47
author
cowan
field
comment
newvalue
oldvalue
8
raw-time
1349369747547809
ticket
17
time
2012-10-04 23:55:47
Change at time 2012-10-04 23:55:47
author
cowan
field
resolution
newvalue
fixed
oldvalue
raw-time
1349369747547809
ticket
17
time
2012-10-04 23:55:47
Change at time 2012-10-04 23:55:47
author
cowan
field
status
newvalue
closed
oldvalue
writing
raw-time
1349369747547809
ticket
17
time
2012-10-04 23:55:47
Change at time 2011-02-22 04:34:18
author
arcfide
field
comment
newvalue
oldvalue
7
raw-time
1298320458000000
ticket
17
time
2011-02-22 04:34:18
Change at time 2011-02-22 04:34:18
author
arcfide
field
owner
newvalue
arcfide
oldvalue
raw-time
1298320458000000
ticket
17
time
2011-02-22 04:34:18
Change at time 2011-02-22 04:34:18
author
arcfide
field
status
newvalue
writing
oldvalue
decided
raw-time
1298320458000000
ticket
17
time
2011-02-22 04:34:18
Change at time 2011-01-29 11:30:33
author
alexshinn
field
comment
newvalue
oldvalue
6
raw-time
1296271833000000
ticket
17
time
2011-01-29 11:30:33
Change at time 2011-01-29 11:30:33
author
alexshinn
field
status
newvalue
decided
oldvalue
assigned
raw-time
1296271833000000
ticket
17
time
2011-01-29 11:30:33
Change at time 2011-01-29 11:30:21
author
alexshinn
field
comment
newvalue
oldvalue
5
raw-time
1296271821000000
ticket
17
time
2011-01-29 11:30:21
Change at time 2011-01-29 11:30:21
author
alexshinn
field
owner
newvalue
oldvalue
alexshinn
raw-time
1296271821000000
ticket
17
time
2011-01-29 11:30:21
Change at time 2011-01-29 11:30:21
author
alexshinn
field
status
newvalue
assigned
oldvalue
reopened
raw-time
1296271821000000
ticket
17
time
2011-01-29 11:30:21
Change at time 2011-01-29 11:30:10
author
alexshinn
field
comment
newvalue
oldvalue
4
raw-time
1296271810000000
ticket
17
time
2011-01-29 11:30:10
Change at time 2011-01-29 11:30:10
author
alexshinn
field
resolution
newvalue
oldvalue
fixed
raw-time
1296271810000000
ticket
17
time
2011-01-29 11:30:10
Change at time 2011-01-29 11:30:10
author
alexshinn
field
status
newvalue
reopened
oldvalue
closed
raw-time
1296271810000000
ticket
17
time
2011-01-29 11:30:10
Change at time 2010-10-18 02:51:55
author
cowan
field
comment
newvalue
The WG voted to accept SRFI-23 `error`.
oldvalue
3
raw-time
1287345115000000
ticket
17
time
2010-10-18 02:51:55
Change at time 2010-10-18 02:51:55
author
cowan
field
resolution
newvalue
fixed
oldvalue
raw-time
1287345115000000
ticket
17
time
2010-10-18 02:51:55
Change at time 2010-10-18 02:51:55
author
cowan
field
status
newvalue
closed
oldvalue
new
raw-time
1287345115000000
ticket
17
time
2010-10-18 02:51:55
Change at time 2010-05-10 03:52:11
author
arcfide
field
comment
newvalue
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.
oldvalue
2
raw-time
1273438331000000
ticket
17
time
2010-05-10 03:52:11
Change at time 2010-05-02 23:59:44
author
cowan
field
comment
newvalue
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.
oldvalue
1
raw-time
1272819584000000
ticket
17
time
2010-05-02 23:59:44
Change at time 2010-05-02 23:59:44
author
cowan
field
milestone
newvalue
oldvalue
raw-time
1272819584000000
ticket
17
time
2010-05-02 23:59:44