b50d01891b
"static" is a keyword in the context of JS classes, no matter how deeply nested. Therefore, keep track of the nesting level. Switching the keywordiness of "static" off during method definition parsing makes no sense as the standard doesn't mention such a thing. Method bodies are strict code where you cannot use "static" as identifier. Methods and properties can be called "static" no matter if static is a keyword or not. Pick-to: 6.4 Fixes: QTBUG-96631 Change-Id: Ia09e52fe2ae72721fe1c8a9b95899a31095db988 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> |
||
|---|---|---|
| .. | ||
| script/com | ||
| translations | ||
| CMakeLists.txt | ||
| dummy_imports.qml | ||
| exporterror1.mjs | ||
| idtranslatable-unicode.js | ||
| idtranslatable.js | ||
| importerror1.mjs | ||
| modulewithlexicals.mjs | ||
| testmodule.mjs | ||
| testregister.mjs | ||
| testregister2.mjs | ||
| testregister3.mjs | ||
| translatable-unicode.js | ||
| translatable.js | ||
| translatable2.js | ||
| tst_qjsengine.cpp | ||