From 7d4fc70e70ca566900c01aa7c5e3ec4770d15933 Mon Sep 17 00:00:00 2001 From: Lars Knoll Date: Mon, 20 Jan 2014 13:51:00 +0100 Subject: Split ManagedVTable into two classes Keep the basic methods in ManagedVTable, but have the Object related stuff in an ObjectVTable class. Change-Id: I9b068acf3caef813686227b8d935e7df1a7d1a6e Reviewed-by: Simon Hausmann --- src/qml/jsruntime/qv4objectiterator_p.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/qml/jsruntime/qv4objectiterator_p.h') diff --git a/src/qml/jsruntime/qv4objectiterator_p.h b/src/qml/jsruntime/qv4objectiterator_p.h index e95f59e247..08a740fc37 100644 --- a/src/qml/jsruntime/qv4objectiterator_p.h +++ b/src/qml/jsruntime/qv4objectiterator_p.h @@ -83,12 +83,12 @@ struct Q_QML_EXPORT ObjectIterator }; struct ForEachIteratorObject: Object { - Q_MANAGED + V4_OBJECT Q_MANAGED_TYPE(ForeachIteratorObject) ObjectIterator it; ForEachIteratorObject(ExecutionContext *ctx, const ObjectRef o) : Object(ctx->engine), it(workArea, workArea + 1, o, ObjectIterator::EnumerableOnly|ObjectIterator::WithProtoChain) { - setVTable(&static_vtbl); + setVTable(staticVTable()); } ReturnedValue nextPropertyName() { return it.nextPropertyNameAsString(); } -- cgit v1.2.3