12.22: todo.adda/oop/subclassing without sideaffects:
. how does the oop remain secure, and yet reusable?
they are having a lot of fun with subclassing,
so, is there any way to do that safely ?
the general idea is that it creates sideaffects,
so not only do you want to enforce capability limits on apps,
you also want to warn users when an app uses side-affecting features .
. you want to bar cap'grabbing features
like the obj'c categories which allow adding slots to library classes;
however, need to get more aquainted with
why they feel that is needed,
and find some alternative .
2011-12-31
Subscribe to:
Post Comments (Atom)
12.8.30: adda/oop/terminology/def subclassing:
ReplyDelete. gof's Design Patterns book transformed the oop industry,
here's what they said about
subclassing's relation to subtyping:
"( subclassing allows our composite widgets
to be usable everywhere that single widgets are,
because they share the same supertype ).
. they expect subclassing to support
subtype polymorphism;
eg, it can't just be a typedef shortcut;
a subclasser has also got to be conforming
to the syntactic and symantic interface
of the type it subclassed from .