> On Mar 10, 2017, at 9:33 AM, Thiago Macieira <thiago.macie...@intel.com> > wrote: > > On sexta-feira, 10 de março de 2017 04:48:18 PST Joerg Bornemann wrote: >> No, but we have tried Duktape a year ago. >> I stopped working on a switch to Duktape because of three things: >> 1. C++-references to JS objects. One had to make sure that the engine >> doesn't garbage collect what you're referencing. That was possible in a >> hacky way. >> 2. Much worse: no way of implementing a QScripClass-like facility. >> Solvable, for sure, but nothing that's done easily along the way. >> 3. The insight that if we have to ship a JS engine anyways it can just >> be QtScript, or a stripped-down version of it for my sake. > > Except that QtScript has a very old JSC engine that hasn't received security > updates, or any updates of any kind, for some time. It would be irresponsible > to use it for new projects. > > Find another, please.
We never said we will continue to use QtScript *as-is*. When I said JSC, I was talking about a modern version of JSC from the WebKit trunk, not the last copy of it that was bundled with QtScript. For standards-compliance & features, JSC is quite attractive as it's the most advanced. > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Jake Petroules - jake.petrou...@qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development