> Toaster Scheme may state that the set of locations is > empty, which still complies with the standard
No; just as you want to be able to be confident that anything labelled "Ultra Scheme" lets you use the <insert favorite feature here> package, I want to be confident that anything labelled "Traditional Scheme" (you haven't yet convinced me that "Core" captures what's needed) will allow me to load Scheme code from a file. If your intention is that Toaster Scheme /not/ be labelled as Traditional Scheme compliant, then you can indeed have something called Core Scheme that's the mutual intersection of all the things anyone wants, but the designation will be useless, because /nobody/ can do /anything/ in an environment that's nothing but Core Scheme, so we'll still need a plethora of kinds of Scheme. What I'm suggesting is that WG2 should do their work in such a way that Toaster Scheme is WG2-Scheme compliant, but not WG1-Scheme compliant. By the way, WG1-Scheme also needs transcript-on and transcript-off, unless it has more primitive output-redirection primitives with which one can write those. And it needs trace. Maybe the right brand is "Hacker Scheme." :-) _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
