Modules
stéphane ducasse
ducasse at iam.unibe.ch
Thu Feb 24 07:06:42 UTC 2005
hi dan
since your last visit we have been looking around and this is
interesting to see that
over the last 4 years a lot of work have been done around a similar
idea but not quite the same
than our classboxes. Even if I do not believe that classboxes are the
solution as is now.
I think that they are interesting.
If you want I can send you some OOPSLA and ECOOP papers
For example,
virtual classes proposes to introduce kind of classes extensions scope
by having inheritance between modules (a hack because they could have
a clean import relationship) and they have the problem that they
duplicate classes from the refection point of view they have two
classes.
Nested Inheritance (OOPSLA 04) proposes somehow the same. The idea is
that from within
a module class name are lookup following some import chain (of course
they have types
and everything is much more complex then) but the basic principle is
to late bound
classname lookup so that local redefinitions takes precedence over the
ones in other scopes.
mixedjuice (ECOOP 2002) they support classes extensions in Java but
everything is static
you cannot have different clients seen different behavior as in
classboxes.
So I have to recompile everything and everybody will see everything.
Again I'm not that this soemthing we want since it can make everything
more complex
(code navigation....)
Stef
More information about the Squeak-dev
mailing list
|