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 #534
cc
changetime
2013-07-07 03:20:44
component
WG1 - Core
description
Michael Montague writes:
I believe that `include-library-declarations` is unnecessary. `include` (and `include-ci`) should be able to include library declarations if used at the <library-declaration> level.
If you want to include code (which is not wrapped in a `begin`) in a library, then use `(begin (include <filename>))`.
id
534
keywords
milestone
owner
alexshinn
priority
major
reporter
cowan
resolution
wontfix
severity
status
closed
summary
Include at the library level should include declarations, not code
time
2013-05-19 23:48:10
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
534
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
534
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
534
time
2013-07-07 03:20:44
Change at time 2013-05-19 23:51:40
author
cowan
field
comment
newvalue
While this position is certainly logical, I believe it represents the wrong balance between logic and convenience. Including code is a far more common and basic use case than including further declarations: most libraries do not require the latter feature at all. In addition, Scheme 48's module system, on which the draft's system was founded, has the same semantics for `include`, which it spells `files`.
oldvalue
1
raw-time
1368982300746853
ticket
534
time
2013-05-19 23:51:40