Re:Kay on the Meaning of "Object-Oriented Programming"
by nvarsj on Tuesday June 07, 2011 @11:20AM
(#2629467)
I think he does mean runtime binding, as with a virtual function call. But probably more extreme - instead of a lookup table to find the static type, a message is simply sent to the receiving object. The object itself then handles it based on its type definition (which itself could be defined at runtime).
[ Parent
| on HN ]
Re:Kay on the Meaning of "Object-Oriented Programming"
by gnaritas on Tuesday June 07, 2011 @11:24AM
(#2629483)
And the object can handle messages for which no function exists at all.
Re:Kay on the Meaning of "Object-Oriented Programming"
by sedachv on Tuesday June 07, 2011 @12:46PM
(#2629867)
This (#doesNotUnderstand:) is not very widely known but extremely important:
http://carcaddar.blogspot.com/2009/04/closure-oriented-metap...
http://people.csail.mit.edu/gregs/ll1-discuss-archive-html/m...