Extension methods, extension classes and extension packages
Avi Bryant
avi.bryant at gmail.com
Fri Mar 25 18:21:41 UTC 2005
On Fri, 25 Mar 2005 18:57:24 +0100, Samir Saidani
<saidani at info.unicaen.fr> wrote:
> Presently, in PackageInfo, there is two methods called
> extensionMethods and extensionClasses which names puzzled me for what
> I want to do :
>
> extension methods : this is methods extending the instance side of a
> current class
>
> extension classes : this is methods extending the side class of a
> current class
I'm not sure which method you're thinking of, but that's not what
#extensionClasses does. It returns a list of the classes that are
extended by the current package, which is to say, all of the classes
for the methods in #extensionMethods.
> In a same way, I propose the following convention :
>
> Collections-Unordered-*SqueakEnh-Collections
>
> (or *<ModifyingPackage>-<Section>-<PackageName>-<Section> but for
> browser displaying categories in alphabetic order, the other one would
> be more convenient)
Apart from the issue of alphabetic order, I don't see what the point
is - why not just put those classes in a normal SqueakEnh-Collections
category?
If what you're doing is really just enhancing another package, I would
also consider simply releasing a new version of that package
(Collections-ss.123.mcz). Anyone should be able to merge that into
their image (or their own version of Collections) if they want your
changes.
Avi
More information about the Squeak-dev
mailing list
|