Andre van Tonder scripsit: > Imports in the middle of a module are a different story. I can see > good reasons for opposing them, technical and otherwise.
If (library ...) wasn't a form wrapping the library, but was just a header for it (as I once proposed), that would make more sense to me. As it is, to find the imports (particularly if a macro is not allowed to expand into an import) is just a matter of calling "read" and then examining the car of each body form. Still and all, although the top level should be able to import anywhere (because it is an emulation of interaction in R5RS), requiring modules to import only at the beginning isn't *that* bad. Maybe compromise is possible on this matter after all. -- John Cowan [email protected] http://ccil.org/~cowan Promises become binding when there is a meeting of the minds and consideration is exchanged. So it was at King's Bench in common law England; so it was under the common law in the American colonies; so it was through more than two centuries of jurisprudence in this country; and so it is today. --Specht v. Netscape _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
