Okay, I'm not familiar with this paper, and I've only read the history intro so far, but it was bad enough I had to stop and comment. It's just wrong on many d

Okay, I'm not familiar with this paper, and I've only read the history intro so far, but it was bad enough I had to stop and comment. It's just wrong on many different levels... For starters, the point about determining which function is going to be called being determined at runtime... That's a function of dynamic binding/function selection, not object orientation. You can have OO software that doesn't have any runtime polymorphism, and you can have non-OO software that is entirely based on dynamic dispatch.... and assuming the logic is such that you really can't know how it will be resolved until runtime, the problem is no better that static code, because the static code effectively becomes an branch based on a dynamically calculated runtime value NO MATTER THE CODING STYLE. I could go on... but I'd have to write as much as the author has.