[gambit-list] Re-importing modules

Adam adam.mlmb at gmail.com
Thu Oct 3 11:47:15 EDT 2019


Hi Lassi,

Thanks for your response.

Manual load semantics is what you get from Gambit.

The reason for using Gerbil as a layer on top of Gambit, is to get
automatic recompile, automatic reimport, automatic reevaluate as automation
of exactly that is essential to incremental dev. ""This (detail) is not
rocket science"", it's perfectly doable, so I wonder was something switched
off or have I misunderstood what Gerbil is etc., so looking forward to
Vyzo's clarification.

Adam


On Thu, 3 Oct 2019 at 23:12, Lassi Kortela <lassi at lassi.io> wrote:

> > I was trying to go through the obvious moves of incremental dev
> >
> >     (import "a")
> >
> >     So far, the correct thing happens: The text "Hello world" is printed
> out.
> >
> >     4. Now, with gsi running, separately in another xterm we alter a.ss
> >
> >     5. In the gsi REPL, we run again:
> >
> >     (import "a")
> >
> > What happens now is a mysterious nothing!
> >
> > This shows that Gerbil does not automatically reimport updated
> dependencies.
>
> For better or worse, many (perhaps most) Scheme implementations behave
> this way. (import ...) is different from (load ...) and does not reload
> already-loaded modules even if you have edited them.
>
> Often one way to solve it is to use `load` after your edits:
>
>      (load "a.ss")
>      (import "a")
>
> I don't know whether this is the "right" way to do it.
>
> _______________________________________________
> Gambit-list mailing list
> Gambit-list at iro.umontreal.ca
> https://mailman.iro.umontreal.ca/cgi-bin/mailman/listinfo/gambit-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20191003/2e32c239/attachment.htm>


More information about the Gambit-list mailing list