[Seaside] Subclasses part II
watchlala at hotmail.com
Sat Jul 4 13:56:29 UTC 2009
Thanks for the help (especially Randal Schwartz) :) I ended up having
several silly little problems (as per below) and one other one where
one class was referenced in memory several times when they should all
have been separate.
> From: stephane.ducasse at free.fr
> To: seaside at lists.squeakfoundation.org
> Subject: Re: [Seaside] Subclasses part II
> Date: Sat, 4 Jul 2009 09:11:26 +0200
> > In my application I have
> > WAComponent < A < B < C.
> > C is calling 'initialize', so therefore I have to also call 'super
> > initialize' all the way up? So each class above C need to have:
> > initialize
> > super initialize.
> > Correct?
> C new
> will call aC initialize (the instance side initialize methods)
> if you did not defined on your C class then the one of the
> superclasses (normal lookup of methods) will be applied.
> Now if you have
> you have to define
> super initialize.
> and recursively on your superclasses too.
> If one method initialize does not do a call to super initialize you
> may break WAComponent behavior that
> relies on having the WAComponent>>initialize method invoked.
> I hope that it is clearer.
> seaside mailing list
> seaside at lists.squeakfoundation.org
Insert movie times and more without leaving Hotmail®.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside