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 #342
cc
changetime
2012-04-05 09:39:08
component
WG1 - Core
description
Currently, `read-bytevector` and `read-bytevector!` return an EOF object at EOF; otherwise, the number of bytes read is returned. Returning 0 at EOF instead would make the result always an exact integer. The only ambiguity would be that reading a bytevector of length 0 (which is to say, not reading any bytes at all) would not report EOF; however, this is a pointless thing to do.
id
342
keywords
milestone
owner
alexshinn
priority
major
reporter
cowan
resolution
wontfix
severity
status
closed
summary
Have READ-BYTEVECTOR(!) return 0 at EOF
time
2012-02-14 05:01:02
type
defect
Changes
Change at time 2012-04-05 09:39:08
author
cowan
field
comment
newvalue
oldvalue
2
raw-time
1333593548392410
ticket
342
time
2012-04-05 09:39:08
Change at time 2012-04-05 09:39:08
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1333593548392410
ticket
342
time
2012-04-05 09:39:08
Change at time 2012-04-05 09:39:08
author
cowan
field
status
newvalue
closed
oldvalue
decided
raw-time
1333593548392410
ticket
342
time
2012-04-05 09:39:08
Change at time 2012-04-05 09:08:17
author
cowan
field
comment
newvalue
The WG voted to reject this proposal.
oldvalue
1
raw-time
1333591697913392
ticket
342
time
2012-04-05 09:08:17
Change at time 2012-04-05 09:08:17
author
cowan
field
status
newvalue
decided
oldvalue
new
raw-time
1333591697913392
ticket
342
time
2012-04-05 09:08:17