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 #238
cc
changetime
2011-09-11 07:48:50
component
WG1 - Core
description
From Denis Washington:
Reading chapter 2 of the third draft, I was thinking: now that we have `#!fold-case` and `#!no-fold-case` and other directives might follow in WG2, wouldn't it be appropriate for section 2.3 (Other notations) to define `#!` as generally introducing a "read directive"? That would encourage implementations to use the same syntax for their own directives, which helps portability (an implementation could just ignore unknown directives which might just be used by another for optimization purposes). Just an idea.
id
238
keywords
milestone
owner
alexshinn
priority
major
reporter
cowan
resolution
wontfix
severity
status
closed
summary
Reserve #! for read directives
time
2011-07-27 00:46:54
type
defect
Changes
Change at time 2011-09-11 07:48:50
author
cowan
field
comment
newvalue
WG1 rejected this proposal.
oldvalue
2
raw-time
1315702130000000
ticket
238
time
2011-09-11 07:48:50
Change at time 2011-09-11 07:48:50
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1315702130000000
ticket
238
time
2011-09-11 07:48:50
Change at time 2011-09-11 07:48:50
author
cowan
field
status
newvalue
closed
oldvalue
new
raw-time
1315702130000000
ticket
238
time
2011-09-11 07:48:50
Change at time 2011-07-27 15:31:53
author
cowan
field
comment
newvalue
Andy Wingo notes:
FWIW, this use is incompatible with scsh-style block comments. Specific tokens can always be special-cased. But treating #!TOKEN as a general read-directive is incompatible with this style of comment.
Guile also has these comments, and they are pervasive, unfortunately.
John Cowan pointed out that a comment-start directive is a kind of read directive.
oldvalue
1
raw-time
1311755513000000
ticket
238
time
2011-07-27 15:31:53