Re: [racket-dev] having zo files from two versions

2015-01-08 Thread Matthew Flatt
I see. If you compile with v5.2.1 first, then it puts files immediately in compiled, and those will be found by v6.1. If you compile v6.1 first, then the files go in a subdirectory of compiled, and they won't interfere with v5.2.1, while v6.1 will continue to find the files in the subdirectory.

Re: [racket-dev] having zo files from two versions

2015-01-08 Thread Dan Liebgold
Actually specifying two different compile root directories seem to work for most things. The exception is my json lib. I have it for 5.2.1 (since it wasn't included in the standard dist). I'd prefer 6.1 to find the standard one, but it's ok if it uses mine instead. The problem is that maybe it

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Matthew Flatt
At Tue, 06 Jan 2015 14:14:22 -0500, Neil Van Dyke wrote: Dan Liebgold wrote on 01/06/2015 02:00 PM: What is a straightforward way to designate the compiled directory to look for zo files in that can be based on the Racket version? I'd like to have Racket 5.2.1 and 6.1 running in parallel

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Neil Van Dyke
Dan Liebgold wrote on 01/06/2015 02:00 PM: What is a straightforward way to designate the compiled directory to look for zo files in that can be based on the Racket version? I'd like to have Racket 5.2.1 and 6.1 running in parallel to aid in upgrading our version. Thanks! I'd like for this

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Dan Liebgold
Hmmm... so this should be as easy to implement as: (use-compiled-file-paths (list (build-path compiled (version Right? Trying it out now. Dan On Tue, Jan 6, 2015 at 11:14 AM, Neil Van Dyke n...@neilvandyke.org wrote: Dan Liebgold wrote on 01/06/2015 02:00 PM: What is a

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Matthew Flatt
Does it work to set PLTCOMPILEDROOTS so that it's used by version 6.1, while version 5.2.1 would still read and write files at the default location? The documentation now tracks changes since v6.0, while changes relative to previous versions are recorded separately (and less usefully) in the

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Matthew Flatt
You probably want to set `current-compiled-file-roots`, which can be initialized by the `PLTCOMPILEDROOTS` environment variable, instead. At Tue, 6 Jan 2015 11:27:35 -0800, Dan Liebgold wrote: Hmmm... so this should be as easy to implement as: (use-compiled-file-paths (list (build-path

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Dan Liebgold
Ok, that seems to be exactly what I'm looking for -- however I tried it and it eventually seems to wind up using just the compiled path during raco setup. Example output is here (I've echoed PLTCOMPILEDROOTS at the top, and note this is under windows): http://pasterack.org/pastes/45913 Is that

Re: [racket-dev] having zo files from two versions

2015-01-06 Thread Dan Liebgold
That method isn't available in 5.2.1, unfortunately. Oh, and wishlist item: the reference docs specify the version the function was introduced in. On Tue, Jan 6, 2015 at 11:39 AM, Matthew Flatt mfl...@cs.utah.edu wrote: You probably want to set `current-compiled-file-roots`, which can be