diff options
author | Lars Knoll <[email protected]> | 2015-01-10 20:51:15 +0100 |
---|---|---|
committer | Lars Knoll <[email protected]> | 2015-01-21 13:18:47 +0100 |
commit | 36662b60b09f636c3623057f8116e862f94ff440 (patch) | |
tree | 1a8a1ee74db89745ea3e327f70229b6b29bb2e62 /src/qml/jsruntime/qv4arraybuffer.cpp | |
parent | 85bf8d732b9651ce7b88d5464b8b3aae138e1893 (diff) |
Remove all the setVTable() calls that aren't required anymore
The memory manager's allocation methods now set this up correctly
for us :)
Change-Id: I8492bf732df601f95a1a851fb3804127ffc83935
Reviewed-by: Simon Hausmann <[email protected]>
Diffstat (limited to 'src/qml/jsruntime/qv4arraybuffer.cpp')
-rw-r--r-- | src/qml/jsruntime/qv4arraybuffer.cpp | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/qml/jsruntime/qv4arraybuffer.cpp b/src/qml/jsruntime/qv4arraybuffer.cpp index 665d7cfced..60ab527a42 100644 --- a/src/qml/jsruntime/qv4arraybuffer.cpp +++ b/src/qml/jsruntime/qv4arraybuffer.cpp @@ -42,7 +42,6 @@ DEFINE_OBJECT_VTABLE(ArrayBuffer); Heap::ArrayBufferCtor::ArrayBufferCtor(QV4::ExecutionContext *scope) : Heap::FunctionObject(scope, QStringLiteral("ArrayBuffer")) { - setVTable(QV4::ArrayBufferCtor::staticVTable()); } ReturnedValue ArrayBufferCtor::construct(Managed *m, CallData *callData) |