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 #214
cc
changetime
2011-09-11 07:51:44
component
WG1 - Reader Syntax
description
From Felix Winkelmann:
{{{
Using "\xX...;" as escape sequence is suboptimal, as it confuses
syntax highlighters. I also have no knowledge of any precedent
of this syntax. Also: how is this sequence handled inside "|...|"?
}}}
id
214
keywords
milestone
owner
alexshinn
priority
major
reporter
alexshinn
resolution
wontfix
severity
status
closed
summary
string/symbol escape sequence confusing
time
2011-06-05 17:28:00
type
defect
Changes
Change at time 2011-09-11 07:51:44
author
cowan
field
comment
newvalue
WG1 rejected this proposal.
oldvalue
2
raw-time
1315702304000000
ticket
214
time
2011-09-11 07:51:44
Change at time 2011-09-11 07:51:44
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1315702304000000
ticket
214
time
2011-09-11 07:51:44
Change at time 2011-09-11 07:51:44
author
cowan
field
status
newvalue
closed
oldvalue
new
raw-time
1315702304000000
ticket
214
time
2011-09-11 07:51:44
Change at time 2011-08-04 04:43:10
author
aag
field
comment
newvalue
From Per Bothner:
For example, with respect to: http://trac.sacrideo.us/wg/ticket/214 says:
Using "\xX...;" as escape sequence is suboptimal, as it confuses
syntax highlighters. I also have no knowledge of any precedent
of this syntax. Also: how is this sequence handled inside "|...|"?
My comment would be:
The precedent is R6RS.
Existing implementations, including Kawa, implement this syntax.
A change in this would be pointless churn - no action is needed.
oldvalue
1
raw-time
1312407790000000
ticket
214
time
2011-08-04 04:43:10