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 #483
cc
changetime
2013-07-07 03:20:44
component
WG1 - Core
description
Sam Tobin-Hochstadt writes:
The draft leaves the semantics of the top level fundamentally unspecified. If this aspect of the charter cannot be portably accomplished, it should not be standardized. Simply describing a feature without saying what it should do is not standardization.
id
483
keywords
milestone
owner
alexshinn
priority
major
reporter
cowan
resolution
wontfix
severity
status
closed
summary
Top-level semantics unspecified
time
2013-05-12 22:20:28
type
defect
Changes
Change at time 2013-07-07 03:20:44
author
cowan
field
comment
newvalue
The WG decided by unanimous consent to take no action on this ticket.
oldvalue
2
raw-time
1373142044410382
ticket
483
time
2013-07-07 03:20:44
Change at time 2013-07-07 03:20:44
author
cowan
field
resolution
newvalue
wontfix
oldvalue
raw-time
1373142044410382
ticket
483
time
2013-07-07 03:20:44
Change at time 2013-07-07 03:20:44
author
cowan
field
status
newvalue
closed
oldvalue
new
raw-time
1373142044410382
ticket
483
time
2013-07-07 03:20:44
Change at time 2013-05-12 22:21:26
author
cowan
field
comment
newvalue
They are not entirely specified, it's true. But there is no reason to force everything to be either 100% specified or 0% specified. A standard is a contract between user and implementer, and it may quite legitimately partly constrain the implementer or user while still providing some freedom of action. No standard, not even highly restrictive ones like ECMAscript 5, constrains everything.
oldvalue
1
raw-time
1368372086178203
ticket
483
time
2013-05-12 22:21:26