diff options
| author | Olivier Goffart <ogoffart@trolltech.com> | 2010-04-16 08:06:39 (GMT) |
|---|---|---|
| committer | Olivier Goffart <olivier.goffart@nokia.com> | 2010-04-19 17:01:22 (GMT) |
| commit | 2649b5f4695680b584decf75af11dc82325cc03f (patch) | |
| tree | 18f82b5ea53bcd39aefd0e9b5bdc320f97e30f82 /.commit-template | |
| parent | 0fd81e81a357edb9f9e615cff28a1876bd363b2e (diff) | |
| download | Qt-2649b5f4695680b584decf75af11dc82325cc03f.zip Qt-2649b5f4695680b584decf75af11dc82325cc03f.tar.gz Qt-2649b5f4695680b584decf75af11dc82325cc03f.tar.bz2 | |
QScript: use JSC::NativeFunctionWrapper instead of JSC::PrototypeFunction when possible
JSC::NativeFunctionWrapper is a typedef to either JSC::PrototypeFunction or
JSC::JSFunction depending if we are running JIT or not.
When using JIT, JSC::JSFunction is faster, as it allow JIT to do the native
call dirrectly. The difference is that in that case, the JS stack is not
fully set up so we have to be carefull.
Unfortunately, it is not possible to make FunctionWrapper inherit from
JSC::NativeFunctionWrapper, because JSFunction is slightly bigger, and we
cannot fit in a Cell
Reviewed-by: Kent Hansen
Diffstat (limited to '.commit-template')
0 files changed, 0 insertions, 0 deletions