[Seaside-dev] Re: [Seaside Commits] Seaside 3.0: Seaside-Tools-Core-lr.15.mcz

[Julian Fitzell]

I guess my point is just that OldClass>>foo is the name of the method
that used to exist and now doesn't. So arguably that's what was
deprecated, even if the deprecation message is now on NewClass>>foo
(the old version didn't have NewClass>>foo so it couldn't really be
deprecated).

It's really a semantic argument though... I don't really care that
much when it comes down to it. So don't worry about it.

Julian

On Mon, Jan 25, 2010 at 10:31 PM, Lukas Renggli <renggli at gmail.com> wrote:
>> Shouldn't the deprecated API refer to the method that used to exist?
>> That makes it easier to compare with code in a 2.8 image, but I guess
>> it makes it harder to find the method you are calling in the 3.0
>> image, so I guess it's not so simple.
>
> Why would you need call it, if the deprecated method was somewhere
> else or renamed?
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>