On May 17, 2009, at 8:26 AM, Michele Simionato wrote:
This is the *last* episode about the module system: http://www.phyast.pitt.edu/~micheles/scheme/scheme24.html I will stop spamming this list with my Adventures now, promised!
Something to ponder. You say: Having compile-time effects affecting run-time values is evil, since it breaks separate compilation. You're talking about inter-library side effects here, where a macro in one library side effects, at expansion time, a value in another library. What if we take the compilation/macro business out of the picture. Say you have one library that, at initialization time, side effects a variable/value "belonging" to another library. Would that be evil too? Justify your answer for full credit. Aziz,,,
