[Pharo-project] DirectoryEntry does not inherit from ArrayedCollection [WAS] Re: [squeak-dev] 3.11 questions
Mariano Martinez Peck
marianopeck at gmail.com
Wed Feb 3 11:01:53 EST 2010
On Wed, Feb 3, 2010 at 4:55 PM, Chris Muller <asqueaker at gmail.com> wrote:
> Extendability, correctness of semantics, and correctness of
> implementation. Inheritance should adhere to an "is-a" relationship;
> because it reflects a specialization of the superclass. A
> DirectoryEntry is definitely not a Collection..
Ahhh I didn't know you were here Chris :) This is cool.
Thanks for the explanations. My question was exactly because it come to my
mind the example of the MethodDictionary or the one I saw yesterday in
VMMaker (Interpreter extends from ObjectMemory).
Then yes, we are interested Chris :) I created the issue:
If you can submit the changes, would be really cool. The instructions to do
that are here:
As far as it is published, it will be integrated in Pharo 1.1.
Thank you very much.
> 2010/2/3 Mariano Martinez Peck <marianopeck at gmail.com>:
> > On Wed, Feb 3, 2010 at 4:34 PM, Chris Muller <asqueaker at gmail.com>
> >> 4) I have refactored DirectoryEntry to no longer inherit from
> >> ArrayedCollection. Is this an improvement with any community
> >> interest?
> > Do you think this is interesting ? What are the benefits of such change
> > Jannik: do we kill a cycle dependency or something with this change ?
> > Kind regards,
> > Mariano
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project at lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev