[plt-dev] Re: problem with optimistic compilation

On Aug 12, Robby Findler wrote:
> On Wed, Aug 12, 2009 at 8:33 PM, Eli Barzilay<eli at barzilay.org> wrote:
> > On Aug 12, Robby Findler wrote:
> >> On Wed, Aug 12, 2009 at 4:45 PM, Eli Barzilay<eli at barzilay.org> wrote:
> >> > On Aug 12, Robby Findler wrote:
> >> >> Okay, after some more thought and offline consultation, I've
> >> >> changed the way DrScheme works wrt to saving compiled .zo
> >> >> files. It now saves its compiled files in compiled/drscheme/ (and
> >> >> compiled/drscheme/errortrace), meaning that the files will be
> >> >> ignored when mzscheme runs. It also only looks in those
> >> >> directories when it is in compiled-file-generation mode.
> >> >
> >> > Won't this have the same problem with multiple versions of
> >> > drscheme using the same file?
> >>
> >> Not unless there is a bug in CM; it should just recompile files when
> >> they are out of date.
> >
> > I'm talking about:
> >
> >  * Create a file
> >  * Run in drscheme, creating a compiled version
> >  * Update PLT to a newer version
> >  * Run the file again -- so the compiled file is still newer, but has
> >    the wrong version.
> >
> > BTW, I tried to check it, but for some reason I don't get any
> > compilation to happen -- is there some option I'm forgetting?
> 
> The file has to be outside of the PLT tree, maybe?

It was outside (I even tried to move it in, with no visible effect).
I just tried it again with no ~/.plt-scheme and didn't get a compiled
directory either.


> What you're describing sounds like it would be a bug in CM. I was
> under the impression that this particular bug does not exist in CM
> but I may be wrong.

I don't know what CM is doing, but I don't see any reason for it to
remove a newer file when the version doesn't match.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!