Move Managed data into it's own subclass

This prepares for moving over to a d pointer scheme,
where Managed subclasses don't hold any data directly. This
is required to be able to move over to a modern GC.

Change-Id: I3f59633ac07a7da461bd2d4f0f9f3a8e3b0baf02
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

1 files changed, 4 insertions, 0 deletions

diff --git a/src/qml/jsruntime/qv4functionobject_p.h b/src/qml/jsruntime/qv4functionobject_p.h
index ef58ffce7f..0160bfd986 100644
--- a/src/qml/jsruntime/qv4functionobject_p.h
+++ b/src/qml/jsruntime/qv4functionobject_p.h
@@ -139,6 +139,10 @@ struct Q_QML_EXPORT FunctionObject: Object {
 
     ReturnedValue protoProperty() { return memberData[Index_Prototype].asReturnedValue(); }
 
+    bool needsActivation() const { return managedData()->needsActivation; }
+    bool strictMode() const { return managedData()->strictMode; }
+    bool bindingKeyFlag() const { return managedData()->bindingKeyFlag; }
+
 protected:
     FunctionObject(InternalClass *ic);