| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A lot of the JSC::ExecState functions rely on scopeChain() not
being 0. This means we shouldn't pop the scope chain if doing so
would make it empty; otherwise when you call e.g. pushScope() or
evaluate(), you will crash. So instead of popping the chain
completely, we now set the sole scope chain item's object pointer to
0 and add appropriate checks elsewhere.
A second issue, not solved in this commit, is that JSC expects
the Global Object to always be the last item in every scope
chain. If it's not, you will crash.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For arguments, we always need to skip the implicit 'this' argument
For line number, we walk thought the stack frames from the top to find
the one above the requested one, which contains the returnPC we need.
Also fixed a crash because QScriptContext::parentContext would have
returned a pointer with flags inside.
Reviewed-by: Kent Hansen
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also fix some autotest failures, improve the descriptions of failures,
and make the tests run to completion.
|
| |
|
|
|
|
|
|
|
| |
In the JSC-based back-end, script-owned QObjects are not always
deleted immediately by the GC. I don't know what precisely
determines the deletion time yet. (Inserting a qDebug() before
evaluate("gc()") seems to fix it, though...)
|
|
|
|
|
| |
Added the properties to the activation object: __extension__,
__setupPackage__ and __postInit__.
|
|
|
|
|
| |
It's an internal function, and currently not implemented
in the JSC-based back-end.
|
|
|
|
|
| |
QScriptContext::backtrace() is implemented now (since commit
34511e1001471ed4041794640aefe508f50ad01c), so the tests work.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It doesn't work for overloaded methods yet (unless you just
happened to call the overload that's defined last in the source
file).
In the old back-end we stored the actual overload that was being
called in the QScriptContextPrivate. Since QScriptContext is a
JSC::ExecState now, we either have to add the information to
JSC::ExecState, or add some mapping scheme so we can go
determine the meta-index for a particular (ExecState, QtFunction)
pair.
Also in this commit: Marked expected failures, so the autotests
will run to completion.
|
|
|
|
|
| |
Look up the property as a normal JS property before falling back
to the dynamic query mechanism. This is the documented behavior.
|
|
|
|
|
| |
Doesn't pass the test yet, but at least it returns something that
might be useful on occasion.
|
|
|
|
|
| |
returnValue() and setReturnValue() are internal functions not
implemented in the JSC-based back-end.
|
|
|
|
|
| |
QScriptValue::scope() and QScriptValue::setScope() are internal
function that we don't implement fully in the JSC-based back-end.
|
|
|
|
| |
Missing parentheses in function expression (JSC requires them).
|
|
|
|
| |
Accept the presence of a JSON object.
|
|
|
|
|
| |
JSObject::getPropertyAttributes() does not follow the prototype
chain, so we have to do it.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
qtscript-jsc-backend
Conflicts:
src/script/api/qscriptable.cpp
src/script/api/qscriptable_p.h
src/script/qscriptclassdata.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The code block associated with QBENCHMARK_ONCE macro will only be executed once,
whether the backend returns a valid result or not. The "-iterations" command line
argument is also ignored.
This is useful for benchmarking code that has side effects.
Revby: jasplin
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The documentation implies that start restarts. Which it did, but only if the
timeline was finished _and_ the duration hadn't been changed meanwhile.
So after a setDuration(), start() would do nothing, which was unexpected.
Merge-request: 1145
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The docs said that the default axis was (0, 0, 1), but the code
and unit tests were using (0, 0, 0). Modify the code to match the
docs because (0, 0, 0) is not very useful. Also optimize the
calculation of sin/cos values for 90, 180, and 270 degrees.
Reviewed-by: Aaron Kennedy
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
in a tree-like model with one of its grand-children being selected.
Added recursive deselection for the model.
Task-number: 232634
Reviewed-by: thierry
|
| | |
| | |
| | |
| | | |
Task-number: 258459
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the current index is invalid, start would be (0,0) but would be
skiped
Task-number: 220195
Reviewed-by: thierry
|
| | |
| | |
| | |
| | |
| | |
| | | |
... by prepending SRCDIR to the loaded files.
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On windows mobile with native menubar integration the menubar is not
a child of the mainwindow
Reviewed-by: Joerg
|
| | |
| | |
| | |
| | |
| | |
| | | |
This extra check prevents a crash if plugin loading fails
Reviewed-by: Joerg
|
| | |
| | |
| | |
| | |
| | |
| | | |
Windows CE is sometimes a little bit slow
Reviewed-by: Joerg
|
| | |
| | |
| | |
| | | |
Reviewed-by: Joerg
|
| | |
| | |
| | |
| | |
| | |
| | | |
We cannot remove a file that's still opened.
Reviewed-by: ossi
|
| | |
| | |
| | |
| | |
| | |
| | | |
There's no time() on Windows CE.
Reviewed-by: Daniel Molkentin
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Win CE doesn't support real file permissions (FAT only).
Further, we don't have pagefile.sys.
Reviewed-by: thartman
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These tests run against domain names in troll.no and to allow shorter
names the machine has to be in this domain.
Removing them since this specific case test the OS more than Qt itself.
Reviewed-by: Thiago
|
| | |
| | |
| | |
| | | |
Reviewed-by: thartman
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The TCP socket must get the chance to read data into its read buffer
after the first read operation emptied it.
Reviewed-by: thartman
|
| | |
| | |
| | |
| | | |
Reviewed-by: thartman
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QProcess is supposed to be reentrant but was not on Unix. The
constructor of QProcessManager could be exectued several time when
QProcess is created. The construction is now protected by a mutex.
Task-number: 254246
Reviewed-by: Olivier Goffart
|
| | |
| | |
| | |
| | |
| | |
| | | |
defaultRowSizes was broken on oxygen style because of missing icons.
Reviewed-by: paul
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
before, it asserted; now, the test is not asserting anymore but
still failing, because the fix is not yet checked in. Additionally,
it now runs from a shadow directory.
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
dnotify is something from older linux kernels and cannot be trusted, therefore
we skip some tests. Also we cannot guarantee that 1 operation on the file give only
1 notification in general, so we relaxed the conditions.
Reviewed-by: paul
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
can not be found change that behavior to warn by default.
Currently the default behavior of include() in a .pro file is not to
warn if the supplied file argument can not be found which can lead to
hard to find build errors. The include() will now,by default, warn if
the specified file can not be found.
If a warning is not required because the included file is optional then
example use in the .pro file:
include(SomePriFile.pri", "", true)
Task-number:259398
Reviewed-by:Marius Storm-Olsen
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
qtscript-jsc-backend
Conflicts:
tests/auto/qscriptjstestsuite/tst_qscriptjstestsuite.cpp
tests/auto/qscriptv8testsuite/tst_qscriptv8testsuite.cpp
|
| | |
| | |
| | |
| | |
| | | |
Apperently we don't get the leave event when simply moving the
mouse with the testlib
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The first VERIFY_COLOR(w.geometry(), w.color); call was failing because
the window was mapped but not yet painted on the screen.
Reviewed-by: Bradley T. Hughes
|