Lazily construct the QScriptActivationObject

We can store flags on the ReturnValueRegister entry in the stackframe
header (as native function don't use that)
Then when requesting an activation object we can lookup the flags to
know if we should create it.

This reduce a lot the cost of a native call.

Reviewed-by: Kent Hansen

1 files changed, 1 insertions, 4 deletions

diff --git a/src/script/bridge/qscriptactivationobject_p.h b/src/script/bridge/qscriptactivationobject_p.h
index eb60ae5d37..8c62b23c95 100644
--- a/src/script/bridge/qscriptactivationobject_p.h
+++ b/src/script/bridge/qscriptactivationobject_p.h
@@ -74,12 +74,9 @@ public:
 
     struct QScriptActivationObjectData : public JSVariableObjectData {
         QScriptActivationObjectData(JSC::Register* registers)
-            : JSVariableObjectData(&symbolTable, registers), calledAsConstructor(false)
+            : JSVariableObjectData(&symbolTable, registers)
         { }
         JSC::SymbolTable symbolTable;
-
-        //specifies if the context of this activation object is called as constructor
-        bool calledAsConstructor;
     };
 
     QScriptActivationObjectData *d_ptr() const { return static_cast<QScriptActivationObjectData *>(d); }