Fix two qqmlecmascript tests (assignSequenceTypes one of them)
authorSimon Hausmann <simon.hausmann@digia.com>
Fri, 7 Jun 2013 20:43:14 +0000 (22:43 +0200)
committerLars Knoll <lars.knoll@digia.com>
Sat, 8 Jun 2013 20:38:57 +0000 (22:38 +0200)
commitaeb5e8319c14721a03c3ab797c893efeb29bb162
treedc50674a32c417d713fa52b4bd281086000ab816
parentdc262bf1981523680da60d0a1060de167abb28e4
Fix two qqmlecmascript tests (assignSequenceTypes one of them)

In various places in the engine we do QVariant(v4Value.booleanValue()),
which unfortunately constructs a QVariant from an unsigned int.

IIRC we used Bool(uint) as type in the run-time to ensure that the compiler
allocates an entire general purpose register for JIT calls on all platforms, so
those functions remain untouched. But I think it's safe to at least change the
getters in Value, as those are never called directly from generated code.

Change-Id: Ia235141b8bcfc38403a7967436c68e73e7eee669
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
src/qml/qml/v4/qv4value_p.h