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 #512

cc


    

changetime

2013-07-07 03:20:44

component

WG1 - Core

description

Aaron Hsu writes:

  The standard has, as a whole, favored the introduction of new procedure names to handle new options for procedures that do effectively the same thing. In some cases this makes a bit of sense, as it would be unwieldy to do otherwise. However, there are other places where this does not make sense, and in particular, places where parameters, which we provide, could more readily be used. These places include procedures that provide behavior which is inherently dangerous and ought not to receive a full procedure name. The `write` procedures come to mind. The `include` and `include-ci` forms also come to mind. Adding more names doesn’t scale well, and I think we’ve gone wrong here.

id

512

keywords


    

milestone


    

owner

alexshinn

priority

major

reporter

cowan

resolution

wontfix

severity


    

status

closed

summary

Parameters should be used instead of proliferating names

time

2013-05-13 08:29:17

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

512

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

512

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

512

time

2013-07-07 03:20:44

Change at time 2013-05-13 08:31:19

author

cowan

field

comment

newvalue

Au contraire.  If that were done, the only way to call `write` with predictable results would be by always wrapping it in a `parameterize` form, which is longer, less clear, and more error-prone (what happens when you set the parameter to a meaningless value?)  The reference to `include` and `include-ci` is misconceived: syntax forms are not affected by the state of (run-time) parameter objects, and without low-level macros there are no such objects at compile time.

oldvalue

1

raw-time

1368408679175732

ticket

512

time

2013-05-13 08:31:19