> In C++, if you try to call obj->method() where `method` is not defined on the object, it won't throw an exception: it simply won't compile. I read the page,

> In C++, if you try to call obj->method() where `method` is not defined on the object, it won't throw an exception: it simply won't compile. I read the page, I liked it. It shows a try/catch is how it'd be done. > In Java, the "class cast exception" is a somewhat different concept. Even if both classes support the same method, you can't cast between them if they don't have a superclass-subclass relationship. I find that fascinating. But still, another case where it's more a rule and intricacy of the language. This is the latest C++17 draft (2017-03-21) http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/n4659.pdf http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/n465.... So here's why I go on about it being an intricacy of the language: The amount of casting / type rules and so on in C++, for instance, is mind-boggling. > The core difference is "late binding" -- in languages like Smalltalk, the mapping from names to methods is evaluated at runtime Which is interesting. And cool. Isn't that similar to, an extent, virtual functions / vtable'd methods in C++? But how does this wrap into C++ not handling an aspect of OOP? In your words. Even though I feel #doesNotUnderstand is a sugar and not necessarily a whole OOP concept, I think it can handled via an event system and try/catches.