Brian Harvey scripsit: > Reading this was enough to convince me that the WG1 \subset WG2 > principle might be wrong. Maybe the two most useful categories aren't > "small" and "large," or "educational" and "industrial," but "optimized > for interaction" and "optimized for optimized compilation." In the > former category, there's nothing inessential about LOAD.
Nowadays, copy and paste might do the trick. :-) > (I do understand that "essential" means "can't be written in terms > of other essential elements of the language" rather than "can't live > without it," In R4RS terms it means nothing of the sort: no rationale whatsoever is given for which features are inessential, but "assoc" can easily be written in terms of other essential features, yet it too is essential; there are many others. > I don't see how to write LOAD without EVAL, which iirc isn't on > anyone's list.) Well, it's in R5RS as a non-optional procedure; it's not in any earlier standard. -- I marvel at the creature: so secret and John Cowan so sly as he is, to come sporting in the pool [email protected] before our very window. Does he think that http://www.ccil.org/~cowan Men sleep without watch all night? _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
