[plt-scheme] On PLaneT packages and compatible upgrades

From: Matthias Felleisen (matthias at ccs.neu.edu)
Date: Wed May 10 08:24:42 EDT 2006

I know. There are many reasons why I am pushing for that. -- Matthias


On May 10, 2006, at 8:02 AM, Robby Findler wrote:

> If we had file export/contract specs separate from the files
> themselves, we could let the implementation behind a version spec vary
> as a minor upgrade (altho the implementation varying could also be a
> major upgrade, if the implementor said so) and require a major upgrade
> if that file changed.
>
> Robby
>
> At Wed, 10 May 2006 07:58:01 -0400, Matthias Felleisen wrote:
>> To be honest, provide-version looks horribly wrong.
>>
>> I would very much prefer a tool -- "Compatible Extension" -- that
>> consumes two modules and either says "yes" or lists the things that 
>> one
>> module exports and the other doesn't. In addition, it should come with
>> an option "Generate Adapter," which produces a module m- with the same
>> interface as m.v0 but with values from m.v1. (This should be N+2 
>> lines:
>> module, import plus one export per m.v0 interface.)
>>
>> (1) I believe this tool is at the order of John's "simple checker" or
>> whatever it's called.
>>
>> (2) It is equally syntactic but it's a first cut.
>>
>> -- Matthias
>>
>> _________________________________________________
>>   For list-related administrative tasks:
>>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
> _________________________________________________
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme



Posted on the users mailing list.