[racket-dev] Shared-instantiation modules

2010-09-10 Thread John Clements
Seems like a FAQ, but: I want to associate a single sound player with a drscheme process. When student code runs, it needs to send messages to that sound player. I want to make sure there's only one running at a time. The first thing that pops into my head is some kind of shared-require

Re: [racket-dev] Shared-instantiation modules

2010-09-10 Thread Ryan Culpepper
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

Re: [racket-dev] Shared-instantiation modules

2010-09-10 Thread John Clements
On Sep 10, 2010, at 8:17 PM, Eli Barzilay wrote: On Sep 10, Robby Findler wrote: 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