> Just two examples: > - Morphic uses a dictionary to allow extensions to add attributes to the > base class. This is closed-world-based-assumption thinking because I have to > know in advance what parts will be extended by someone else. This should be > easily changeable with slots given that slots are manipulate-able at runtime > (ideally).
Since I have several classes that inherit from a superclass that provides a property-dictionary, I'm interested to better understand what you mean by needing to know in advance what parts will be extended by someone else?
