[racket-dev] Shared-instantiation modules

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Fri Sep 10 18:16:21 EDT 2010

FWIW, this is one path that tools can use to circumvent DrRacket's
property (well, the property we work towards anyways) that no program
can cause DrRacket itself to crash or freeze. So if you do provide
things to the user's program in this manner, please try to keep that
invariant in mind.


On Fri, Sep 10, 2010 at 5:04 PM, John Clements
<clements at brinckerhoff.org> wrote:
> On Sep 10, 2010, at 1:48 PM, Ryan Culpepper wrote:
>> The way the rackunit tool does it (to make the rackunit gui DrRacket-aware) is to attach a module into the user namespace on every execution by overriding the 'reset-console' method of drracket:rep:text%. See rackunit/tool.rkt for the code.
>> Then you can have a module/teachpack that just requires the attached module.
> Good Gravy!  It would have taken me *weeks* to figure that out. Especially the bit about making the shared link module written in the #%kernel language. Yikes!
> It works like a charm.
> Many thanks,
> John
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev

Posted on the dev mailing list.