Avoid creating a separate Scope in the ExecutionContextSaver

There's no reason this class should create a scope on it's own.

Change-Id: I93bddea8be42a908a1aca1bcb0ec867aae0d29f8
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

1 files changed, 7 insertions, 7 deletions

diff --git a/src/qml/jsruntime/qv4scopedvalue_p.h b/src/qml/jsruntime/qv4scopedvalue_p.h
index 7df723e9d0..f6cb6fda5d 100644
--- a/src/qml/jsruntime/qv4scopedvalue_p.h
+++ b/src/qml/jsruntime/qv4scopedvalue_p.h
@@ -401,19 +401,19 @@ struct ScopedProperty
 
 struct ExecutionContextSaver
 {
-    Scope scope; // this makes sure that a reference to context on the JS stack goes out of scope as soon as the context is not used anymore.
+    ExecutionEngine *engine;
     ExecutionContext *savedContext;
 
-    ExecutionContextSaver(const Scope &scope)
-        : scope(scope.engine)
+    ExecutionContextSaver(ExecutionEngine *engine)
+        : engine(engine)
     {
-        savedContext = scope.engine->currentContext;
+        savedContext = engine->currentContext;
     }
     ~ExecutionContextSaver()
     {
-        Q_ASSERT(scope.engine->jsStackTop > scope.engine->currentContext);
-        scope.engine->currentContext = savedContext;
-        scope.engine->current = savedContext->d();
+        Q_ASSERT(engine->jsStackTop > engine->currentContext);
+        engine->currentContext = savedContext;
+        engine->current = savedContext->d();
     }
 };