Hi

I was thikning that to avoid that, we could record refactoring at least 
method remove and method rename and keep a log so that with a tool I 
can test my application against the current distribution and the 
analysis would tell me where stuff had changed.

This is a general problem that's why using pattern such as deprecation 
are important and this is not by having a global image of 30 GB that we 
will solve the problem.

Stef



On Thursday, May 8, 2003, at 11:10 PM, goran.krampe at bluefish.se wrote:

> Doug Way <dway at riskmetrics.com> wrote:
> [SNIP]
>> There will still always be the "Full" image concept, though, with all 
>> of the
>> development and media content of the traditional Squeak image.  I 
>> agree that
>> we do need to make the Full image content easily available to 
>> everyone, so
>> that we can do all that good stuff like finding all 
>> senders/implementors.
>
> Just want to reiterate that this is false. You can not possibly find 
> all
> senders and implementors just by using the current Full image. There 
> are
> over 230 packages on SM right now. This means there are TONS of code
> outside of the image as we speak. And that is how it always has been.
>
> It was only the lucky few apps that got into the image that have been
> saved from the code rot.
>
> regards, Göran
>