> I don't think that's possible.
Please elaborate on the reason. Would we run into problems if we tried
to specify a super-minimal contract about what guarantees present and
future keyword systems provide to help SRFI writers?
A SRFI has to be implementable and usable as written. It has to give specimens of procedure calls that will actually work for users, and its sample implementation has to be based on procedures and syntax that actually exist. An abstract description is not sufficient.
(Below .sig chosen at random from my list; no personal reference intended!)
John Cowan
http://vrici.lojban.org/~cowan xxxxxx@ccil.orgThat you can cover for the plentiful and often gaping errors, misconstruals
and disinformation in your posts through sheer volume -- that is another
misconception. --Mike to Peter