|
Class: Lookup
Object
|
+--Lookup
|
+--ActiveObject::RedirectingLookup
|
+--BuiltinLookup
|
+--NamespaceAwareLookup
- Package:
- stx:libbasic
- Category:
- Kernel-Extensions
- Version:
- rev:
1.8
date: 2016/12/06 20:00:21
- user: mawalch
- file: Lookup.st directory: libbasic
- module: stx stc-classLibrary: libbasic
accessing
-
builtin
-
initialization
-
initialize
-
do we really need this?
lookup
-
lookupMethodForSelector: selector directedTo: initialSearchClass
-
Following C code is just a performance optimization.
It is not necessary, however it speeds up UI code,
since it heavily uses perform:
-
lookupMethodForSelector: selector directedTo: initialSearchClass for: aReceiver withArguments: argArrayOrNil from: sendingContext
-
This method is no longer sent by the VM as it nows pass
inline/poly cache object.
** This is an obsolete interface - do not use it (it may vanish in future versions) **
-
lookupMethodForSelector: selector directedTo: initialSearchClass for: aReceiver withArguments: argArrayOrNil from: sendingContext ilc: ilcCache
-
Invoked by the VM to ask me for a method to call.
The arguments are: the selector, receiver and arguments,
the class to start the search in (for here-, super and directed sends)
the sending context and the inline/poly cache (instance of
PolymorphicInlineCache).
The returned method object will NOT be put into the inline- and
polyCache bu default. To update the call site's cache, you have to
call ilcCache bindTo: method forClass: initialSearch class. If you
don't call it, inline/poly cache won't be updated and next call
won't be cached (therefore it will be relatively slow.
If I return nil, a doesNotUnderstand: will be send.
|