Edit | Rename | Upload | Download | Back to Top |
Two independently developed modules may have clashing definitions for some shape or behavior so alterations to Smalltalk binding and/or dispatch are needed to have modules with conflicting definitions cooperate in one application.
I very much like the Forth name lookup mechanism where the application code can freely mix vocabularies into a lookup chain.
My general impression is that it is easier to model a resolution to clashing behavior definitions than to clashing shape definitions, #copy and #initialize are troublesome when parts of the shape are unknown to or invisible in the invoking module.
Edit | Rename | Upload | Download | Back to Top |