|
|
|
|
|
by ogogmad
1600 days ago
|
|
> Python's OOP is awkward with object.f() meaning something different from f(object), when really they ought to mean the same thing. >> Why should they? Coming from other OO languages, I would expect `object.f()` to involve a vtable lookup Low level details like that should not concern me. In which case, maybe `f(object)` should do a vtable lookup then; why not? The syntax `object.f()` and `f(object)` should be interchangeable in all situations. |
|