On May 6, 2009, at 12:20 PM, Michele Simionato wrote:
On Wed, May 6, 2009 at 11:08 AM, Derick Eddington
<[email protected]> wrote:
Why aren't you
complaining about how in PLT an explicit phasing (for --- expand)
does
not instantiate the library at run-time? But you want an equivalent
import form in implicit phasing to do so...
In PLT different phases have different instances, so a library can be
instantiated at expand time but no at run-time.
Right, but so can Ikarus. We said this so many times already.
I have shown you examples of how a library may be instantiated
at one time but not another.
In implicit phasing there is a single instance for all phases,
No there isn't! (are we hitting another communication barrier?)
I'm officially confused with where you're coming from and where
you're going with this argument. Sorry.
so I expect an imported library to be instantiated both a compile
time and at runtime, even if it may be a waste (I am not arguing
it is not a waste).
Your expectations are influenced by prior experience in other
languages and systems. They certainly are not a consequence of
what implicit phasing guarantees (or does not guarantee).
Let me declare officially that I am not fond of side effects and I
dislike designs based on side effects; nevertheless, I use side
effects for logging and debugging, so I do have modules depending
on side effects when developing/debugging an application.
We all do that for debugging and what have you. What we do not
do is have the meaning of a library depend on compile-time side
effects that happen when other libraries are compiled/visited/
invoked (like the example you're copying from the you-want-it-
when paper).
Aziz,,,
