On Tue, 3 Jul 2007, Lucas Dixon wrote:
> Andreas Rossberg wrote:
> > "Lucas Dixon" <[EMAIL PROTECTED]>:
> >>
> >> Given the modular design Alice, I suspect this should be easy, I
> >> would guess that the top-level is just an incrementally compiled
> >> module. So it should be possible to end the module and pickel it.
> >
> > It's not that simple. The main problem is that Alice does not allow
> > pickling of resources. So you cannot just pickle the continuation of
> > the interactive loop, since it will certainly contain resources like
> > I/O streams etc. Even if you factorise away this problem, you cannot
> > pickle the current dynamic environment of the toplevel loop, since it
> > will likewise contain resources.
>
> I was not imagining pickling the interactive loop itself, which will
> have a IO stream to stdin/stdout, but the result of it.
My impression is that pickling (and resources) is not the main concern
here. The main problem is not so much persistance, but being able to
``use'' ML sources at runtime, affecting the global compiler environment
(and mutable values), but continuing execution as expected.
A few weeks ago, just before I left for vacation, there was a proposal to
use the component manager of Alice to bring compiled code back into the
current toplevel. What happened to that attempt?
Makarius
_______________________________________________
alice-users mailing list
[email protected]
http://www.ps.uni-sb.de/mailman/listinfo/alice-users
