On Fri, Jan 13, 2012 at 4:48 PM, Mariano Martinez Peck < [email protected]> wrote:
> > > On Fri, Jan 13, 2012 at 4:44 PM, Guillermo Polito < > [email protected]> wrote: > >> But they are both defined the same way! >> >> Array variableSubclass: #WeakActionSequence >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Kernel-Objects' >> >> The only reference to it's weakness it its name! :P >> >> > I also see > > >> asActionSequenceTrappingErrors > > ^WeakActionSequenceTrappingErrors withAll: self > > > ;) > > But ActionSequence is the same jahahahha > >> On Fri, Jan 13, 2012 at 12:39 PM, Henrik Johansen < >> [email protected]> wrote: >> >>> >>> On Jan 13, 2012, at 4:33 23PM, Guillermo Polito wrote: >>> >>> > In 1.3 they look the same, in 1.4 ActionSequence is not there any >>> more... >>> > >>> > Is the second one replacing the first one? are there any differences >>> for the user? >>> > >>> > Thanks, >>> > Guille >>> >>> >>> ActionSequence was not referenced by the base system any more, not sure >>> why it was removed instead of deprecated. >>> And yes, there is a difference for a user, the WeakActionSequence holds >>> actions weakly, while ActionSequence held them strongly. >>> (WeakActionSequence automatically removes the actions when there are no >>> other references to the registrar, while ActionSequence did not, and you >>> had to unregister manually before it would stop executing them) >>> >>> Cheers, >>> Henry >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com
