multiple classes with the same name, namespaces
Craig Latta
craig at netjam.org
Fri Jun 2 01:17:59 UTC 2006
Hi Ralph--
> > When we encounter an occurrence of "Smalltalk at:", we can find all
> > the classes in the system which have the given name. We don't have
> > to use >>allSubclasses since we'll have a cache of all classes in
> > the system (recall my proposed replacement for the current system
> > dictionary).
>
> I don't understand your replacement for the current system dictionary.
> It is just an unkeyed collection of classes. Why bother, when you
> can already ask Class for its instances, or Object for its subclasses?
> Why duplicate functionality?
Oh, I just assumed some uses might want faster access to that bunch of
objects than by trolling the hierarchy; but if there aren't any, then
great, let's discard it. :)
> Class names are not dynamic if you want source code to work. If you
> change the name of a class then you have to find code that refers to
> the class and patch it.
Right, so you do that. I don't accept that as an argument for class
names not being dynamic. It's like saying that objects with dependents
aren't dynamic. Perhaps I'm missing something.
thanks,
-C
--
Craig Latta
improvisational musical informaticist
www.netjam.org
Smalltalkers do: [:it | All with: Class, (And love: it)]
More information about the Squeak-dev
mailing list
|