The former. And maybe there is a problem with drracket sharing too much with the user program too.
Robby On Wednesday, January 16, 2013, Sam Tobin-Hochstadt wrote: > Do you mean the "automatically populate compiled directories" setting, > or the "online compilation"? > > Sam > > On Wed, Jan 16, 2013 at 10:37 AM, Robby Findler > <ro...@eecs.northwestern.edu <javascript:;>> wrote: > > It may be possible to change drracket to only set that parameter when it > is > > compiling files, but for now I think you have to disable drracket's auto > > compilation (in the language dialog's show details section) to develop > > programs like this. > > > > Robby > > > > > > On Wednesday, January 16, 2013, Sam Tobin-Hochstadt wrote: > >> > >> I'm not sure if this is a bug or not, so I'm bringing it up on the > >> list. But when I do the following: > >> > >> #lang racket > >> (require compiler/cm) > >> (manager-compile-notify-handler displayln) > >> (managed-compile-zo > >> > "/home/samth/sw/plt/collects/tests/typed-racket/succeed/null-program.rkt") > >> > >> Then the compiler places the compiled files in the > >> `compiled/drracket/` directory, and looks for compiled files there as > >> well. The `displayln` handler shows that basically all of Racket is > >> being recompiled. I found this quite surprising, and worse it means I > >> can't use DrRacket to develop this program. Would there be a way for > >> DrRacket not to change whatever parameter is being changed here in the > >> user program's context? > >> > >> Sam > >> _________________________ > >> Racket Developers list: > >> http://lists.racket-lang.org/dev >
_________________________ Racket Developers list: http://lists.racket-lang.org/dev