Thanks for the usual rant. This is good to have you here because we could have forgotten. Now of course we apply deprecation (we are probably the guy responsible to get the methods in Squeak long long time ago) but there are moments when there is too much to deprecate or when people forget. And forgetting is humane. Now if your company has lot of money, we can hire another engineer and work full speed and apply even more software engineering practices. Now it does not mean that we do not pay attention. We pay attention to people and to their product. May be each community needs its pain in the ass after all it shows that we get cooler and cooler. But it would be nice if you could give us a break.
Stef On Dec 31, 2010, at 10:22 AM, Levente Uzonyi wrote: > On Thu, 30 Dec 2010, John McIntosh wrote: > >> Well the question as pointed out was does this vm support weak object >> finalization? and since all closure vm support finalization, then >> asking the question was mute, so it was ditched. Sophie from the 2003 >> era had to ask. > > The need for the check it outdated, but the method is still sent by external > packages. With proper deprecation policy the method would be still available. > It would simply return true and raise a deprecation warning. > > > Levente > >> >> >> On 12/30/10, Schwab,Wilhelm K <[email protected]> wrote: >>> Hopefully that can eventually be said as "backward compatibility with good >>> stuff is a priority for Pharo." Moving targets are perhaps best left >>> moving for now. >>> >>> >>> >>> ________________________________________ >>> From: [email protected] >>> [[email protected]] On Behalf Of Levente Uzonyi >>> [[email protected]] >>> Sent: Thursday, December 30, 2010 6:13 PM >>> To: [email protected] >>> Subject: Re: [Pharo-project] WeakArray>>isFinalizationSupported >>> >>> (or so) which is unrelated. The method was removed during a "cleanup". And >>> as you know, backwards compatibility is not a priority for Pharo. >>> >>> >>> Levente >>> >>> >>> >> >> >> -- >> =========================================================================== >> John M. McIntosh <[email protected]> >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> =========================================================================== >> >> >
