<br><div class="gmail_quote">On Fri, Jul 3, 2009 at 2:21 AM, Noel Welsh <span dir="ltr"><<a href="mailto:noelwelsh@gmail.com">noelwelsh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
It would be a big productivity boost for certain applications to have<br>
on demand module loading. This means something like scheme/enter: scan<br>
the filesystem and reload any modules that have changed since the last<br>
time the code was run.<br>
<br>
Is there any downside to just using scheme/enter? Scanning the code,<br>
it seems the use of [compile-enforce-module-constants #f] will slow<br>
things down. I can't see any other downside, and it should be possible<br>
to get around this by loading the code into a new namespace each time.<br>
</blockquote><div><br>IIRC, scheme/enter works at the top-level and "enters" into the namespace of the module you are loading. My guess is that you are looking for something similar to what I asked about in the following thread:<br>
<br><a href="http://list.cs.brown.edu/pipermail/plt-scheme/2008-October/028094.html">http://list.cs.brown.edu/pipermail/plt-scheme/2008-October/028094.html</a><br><br>I implemented a mechanism call dyn-require that mimics dynamic-require, which checks whether the module had changed and reload if necessary. <br>
<br>The basic idea is to replace <br><br>(dynamic-require <module> 'symbol)<br><br>to <br><br>(dyn-require <module> 'symbol) <br><br>This doesn't handle dependency reloading (I thought about it but it seems to open a can of worms so I didn't go down that route) and can share dependencies as well (to ensure the depended structs are the same ones).<br>
<br>If this sounds like what you are looking for - let me know and I'll send you the code.<br><br>Thanks,<br>yc<br><br></div></div>