4 ms·
So I don't know much about anything, but I'm confused on this point. You say "This effectively means it always performs late binding and invoking a message is
by joeblau 13y ago
So I don't know much about anything, but I'm confused on this point. You say "This effectively means it always performs late binding and invoking a message is REALLY slow in Objective-C." But I can't find any evidence of Objective-C performing late binding or in documentation [1][2][3][4].
[1] - http://stackoverflow.com/questions/5943949/late-binding-vs-dynamic-binding http://stackoverflow.com/questions/5943949/late-binding-vs-d...
[2] - http://www.gnu.org/software/gnustep/resources/ObjCFun.html http://www.gnu.org/software/gnustep/resources/ObjCFun.html
[3] - http://developer.apple.com/library/ios/#documentation/general/conceptual/DevPedia-CocoaCore/DynamicBinding.html http://developer.apple.com/library/ios/#documentation/genera...
[4] - http://stackoverflow.com/questions/9470824/dynamic-binding-late-binding-in-java-or-not http://stackoverflow.com/questions/9470824/dynamic-binding-l...
- invalidname 13y agoThe original article seemed to have a mistake there, it now says dynamic binding. This is indeed much slower than regular invocation as the first article you linked to states.
- Roboprog 13y ago"Late binding" is a generalized term for associating a symbol with a value/code at run time, instead of compile/link time. (even if the term is not literally used in the obj-C docs)