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 #315
cc
changetime
2012-04-05 09:35:55
component
WG1 - Core
description
We should probably make (string-set! str n #\null) unspecified.
id
315
keywords
milestone
owner
alexshinn
priority
major
reporter
alexshinn
resolution
wontfix
severity
status
closed
summary
null character may not be usable in strings
time
2011-12-17 15:50:05
type
defect
Changes
Change at time 2012-04-05 09:35:55
author
cowan
field
comment
newvalue
oldvalue
3
raw-time
1333593355004359
ticket
315
time
2012-04-05 09:35:55
Change at time 2012-04-05 09:35:55
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1333593355004359
ticket
315
time
2012-04-05 09:35:55
Change at time 2012-04-05 09:35:55
author
cowan
field
status
newvalue
closed
oldvalue
decided
raw-time
1333593355004359
ticket
315
time
2012-04-05 09:35:55
Change at time 2012-04-05 09:24:09
author
cowan
field
comment
newvalue
The WG decided to reject this proposal.
oldvalue
2
raw-time
1333592649225527
ticket
315
time
2012-04-05 09:24:09
Change at time 2012-04-05 09:24:09
author
cowan
field
status
newvalue
decided
oldvalue
new
raw-time
1333592649225527
ticket
315
time
2012-04-05 09:24:09
Change at time 2011-12-17 23:04:01
author
cowan
field
comment
newvalue
No, we should not! C does strings by convention, but every more recent language I know of, even C++, has a string data type that can handle any character.
In particular, there is no need for this, because we already license implementations to forbid particular characters in strings.
oldvalue
1
raw-time
1324134241811087
ticket
315
time
2011-12-17 23:04:01