PackageInfo ... where?

goran.krampe at bluefish.se goran.krampe at bluefish.se
Tue Oct 14 09:59:49 UTC 2003


"Andreas Raab" <andreas.raab at gmx.de> wrote:
[SNIP]
> In which case having the method belong to the
> original package is really The Right Thing to do. And yes, that'll cause you
> lots of headaches in how to manage a package you hacked. And again, maybe
> that's not such a bad thing - maybe you should add a "proper hook" and feed
> that back to the original package for integration.

Personally I think such a model would be interesting to try

It reminds me of Daniel's very interesting arguments about namespaces.
In short, he was making the point that namespaces "hide" all the
conflicts that really should be detected and worked out by
merging/refactoring between developers instead of just leading to
duplication of code.

If I have a class in my namespace implementing say RSS and you have one
too - then we will not get any kind of conflict and thus the duplication
will go "undetected".

The same theory applies in this case it seems. If you end up using
extension methods they should most probably be fed back to the
maintainer of the package that you are extending.

regards, Göran



More information about the Squeak-dev mailing list