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 #156

cc


    
changetime

    
2012-10-05 12:11:59

    
component

    
WG1 - Core

    
description

    
The following situations are described in draft 1 (and R5RS) with "an error is signalled":

 1. The ''file-spec'' given to `call-with-input-file`, `call-with-output-file`, `open-input-file`, or `open-output-file` represents a file that cannot be opened.

 2. An end of file is read from a port by `read` after the beginning of an object's external representation, but the external representation is incomplete and therefore not parsable.

I propose that in both cases the implementation be required to raise an exception as if by applying `raise` (that is, non-continuably) to an implementation-defined object, which means it can be caught by the R7RS exception system.  Note that there is no requirement to create a fresh object.

    
id

    
156

    
keywords

    

    
milestone

    

    
owner

    
cowan

    
priority

    
major

    
reporter

    
cowan

    
resolution

    
fixed

    
severity

    

    
status

    
closed

    
summary

    
Replace "an error is signalled" with "an implementation-dependent object is raised as if by `raise`"

    
time

    
2011-04-17 05:55:06

    
type

    
defect

    
Changes

    
Change at time 2012-10-05 12:11:59

    
author

    
cowan

    
field

    
comment

    
newvalue

    

    
oldvalue

    
4

    
raw-time

    
1349413919010545

    
ticket

    
156

    
time

    
2012-10-05 12:11:59

    
Change at time 2012-10-05 12:11:59

    
author

    
cowan

    
field

    
resolution

    
newvalue

    
fixed

    
oldvalue

    

    
raw-time

    
1349413919010545

    
ticket

    
156

    
time

    
2012-10-05 12:11:59

    
Change at time 2012-10-05 12:11:59

    
author

    
cowan

    
field

    
status

    
newvalue

    
closed

    
oldvalue

    
writing

    
raw-time

    
1349413919010545

    
ticket

    
156

    
time

    
2012-10-05 12:11:59

    
Change at time 2011-07-11 10:16:02

    
author

    
cowan

    
field

    
comment

    
newvalue

    

    
oldvalue

    
3

    
raw-time

    
1310354162000000

    
ticket

    
156

    
time

    
2011-07-11 10:16:02

    
Change at time 2011-07-11 10:16:02

    
author

    
cowan

    
field

    
owner

    
newvalue

    
cowan

    
oldvalue

    
alexshinn

    
raw-time

    
1310354162000000

    
ticket

    
156

    
time

    
2011-07-11 10:16:02

    
Change at time 2011-07-11 10:16:02

    
author

    
cowan

    
field

    
status

    
newvalue

    
writing

    
oldvalue

    
decided

    
raw-time

    
1310354162000000

    
ticket

    
156

    
time

    
2011-07-11 10:16:02

    
Change at time 2011-07-10 18:14:14

    
author

    
alexshinn

    
field

    
comment

    
newvalue

    
We voted to make this clear.

    
oldvalue

    
2

    
raw-time

    
1310296454000000

    
ticket

    
156

    
time

    
2011-07-10 18:14:14

    
Change at time 2011-07-10 18:14:14

    
author

    
alexshinn

    
field

    
resolution

    
newvalue

    

    
oldvalue

    

    
raw-time

    
1310296454000000

    
ticket

    
156

    
time

    
2011-07-10 18:14:14

    
Change at time 2011-07-10 18:14:14

    
author

    
alexshinn

    
field

    
status

    
newvalue

    
decided

    
oldvalue

    
new

    
raw-time

    
1310296454000000

    
ticket

    
156

    
time

    
2011-07-10 18:14:14

    
Change at time 2011-04-18 07:26:51

    
author

    
arcfide

    
field

    
comment

    
newvalue

    
I like the general idea. I might also suggest that the language signally an error be considered synonymous with raising an appropriate condition using `raise`.

    
oldvalue

    
1

    
raw-time

    
1303086411000000

    
ticket

    
156

    
time

    
2011-04-18 07:26:51