[racket-dev] Running in DrRacket changes behavior of the `compiler/cm` library

The change to DrRacket that you suggest would have the effect of debugging
annotations being forgotten for files that are already compiled by another
route, so that seems wrong.

Robby


On Sat, Feb 2, 2013 at 5:39 PM, Danny Yoo <dyoo at hashcollision.org> wrote:
>
> >
> > With this in place, PLaneT2 package installation appears to be behaving.
>
>
> The other hack in there that's making me feel a little uncomfortable is
this:
>
>
https://github.com/dyoo/racket/commit/df221a6266dc347556e19b98e091b8a62ef8bc8b
>
>
>
> If I don't do this, then as soon as I do the following interaction:
>
> ---
> #lang racket
> (require planet2)
> (install "sxml")
> ---
>
> followed by:
>
> ---
> #lang racket
> (require sxml)
> ----
>
>
> then DrRacket again tries to compile sxml with DrRacket debug
> annotations.  But I do not understand this at all!  Shouldn't the
> module loader be looking at all the paths in use-compiled-file-paths
> before deciding to recompile?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20130202/49abc7f1/attachment.html>