On Tue, May 5, 2009 at 7:24 AM, Ramana Kumar <[email protected]> wrote: > I'll admit I haven't followed your discussion of expansion-time > side-effects in full detail. > But I must ask what you mean to say when you write "(import (x))". > As I understand it, an import form is not an instruction to execute > anything, rather, it is specifying where the bindings in the following > library or script come from. Is there anything we want to agree that > an import form should do apart from making bindings visible (which is > almost a conceptual thing)? If so, what would it be?
An import form does many things: - at visit time/compile time, makes sintax definitions/regular bindings visible - at runtime, execute whatever is in the body of the module It can have side effects at both times.
