Good work with extending the table. I have some comments, many of which are typos or omissions:

Modifications:

260: "generated-symbnols" should be "generated-symbols"
253: "data-type-checing" should be "type-checking" (per Artyom Bologov's request)
189: "maybe-and-either": more descriptive name
167: "ordered-key-value-store"
166: "show", because that is the name of the Chibi library it was derived from
165: "environment": shorter name
120: "timers": The implementation is based on a withdrawn SRFI, but the specification is not
111: "boxies" should be "boxes"
28: "basec-format-strings" should be "basic-format-strings"

221 is labeled incorrectly.

Additions:

235: "combinators"
216: "sicp": this library name is mentioned in the text of the SRFI
201: "extensions": The extensions can be implemented portably, if an extension allows one to shadow core bindings.

Unknowns:
221 recommends the procedures be placed into SRFI-158's library. 162 recommends the procedures be placed into SRFI-128's library. I think these should be moved to the unassigned section.

_______________________________________

I also still believe that all SRFIs that introduce new identifiers should be given library names, even if they also introduce reader syntax. Any system that includes those SRFIs with their reader syntax will most likely use the library system to manage the identifiers introduced in the SRFI.

This would add a lot of the SRFI's that are currently in the "omitted" section except for those with pure reader syntax or have behavior that would be difficult to introduce using the library system (like SRFI-0, SRFI-188, etc.)

I would also move SRFI-34,35, and 36 to the included section because although their behavior was subsumed by R6RS, they are not a part of R7RS-small.

-- Peter McGoron

Reply via email to