Lines Matching full:chain
582 <rdar://problem/6111648> JavaScript exceptions fail if the scope chain includes the global object
586 chain as an indicator of function or global scope activation.
588 global object is injected into the scope chain with 'with'.
3244 JSArray::getItem -- need to handle properties from the prototype chain
3894 prototype chain to start with the string prototype and not create a
4295 The two loops up the prototype chain both need to start from this; instead the
8107 chain. Because of that, we do a getPropertySlot, not getOwnPropertySlot, which works
8762 *before* deref'ing the scope chain, since the profiler uses the scope chain.
8772 chain, since the profiler uses the scope chain.
9262 Track global this value in the scope chain so we can retrieve it
9378 (KJS::resolveBase): Check for being a the end of the scope chain
10240 off, don't use the scope chain. Inside eval, the scope chain doesn't
10365 (KJS::Machine::privateExecute): Separated scope chain deref from
10369 to deref the scope chain.
10783 * VM/Machine.cpp: Factored out scope chain updating into a common
10793 storage type for scope chain data.
10862 directly from the scope chain, instead of from the ExecState.
10871 the scope chain.
11547 (2) Push the name object on the function's scope chain, rather than
11548 the ExecState's scope chain because, well, that's where it belongs.
12100 current call frame's scope chain is an activation: it can be the global
12622 chain in global scope, so we would leak ScopeChainNodes when exceptions
12627 Scope chain reference counting is still wrong in a few ways. I thought
12772 that is what is now kept there, and there is no more need to keep the scope chain in
12804 chain.
13070 - fixed "SquirrelFish crashes due to bad scope chain on some SunSpider tests"
13395 Pass a function body node its function's scope chain, rather than the
13396 current execution context's scope chain, when compiling it.
13399 chain during compilation.
14542 Activation tear-off and scope chain pushing is obsolete because we
18849 Avoid heap allocating the root scope chain node for eval and closure free functions
18852 or closures as they are unable to ever capture the scope chain. This gives us a 2.4%
19012 (KJS::JSObject::put): When walking prototype chain, instead of
19015 prototype chain.
20841 an empty scope chain. The bottom function already returns 0 for that case,
22456 - rolled scope chain optimization out; it was breaking the world
22553 you copy the scope chain.
27879 (compile_branch): Removed branch chain and some unused ESC values.
28546 the longest collision chain is not any longer.
