Hi, On 13/10/2011, at 12:55 AM, ext [email protected]<mailto:[email protected]> wrote:
Hi Aaron, I wonder if this monlithic design was needed to give V8 its traits ? Yes. V8 is designed to run JavaScript super fast, at the expense of everything else. It is elegantly structured internally, but it is very clearly a JavaScript engine first. It might be more work, but we could try and "borrow" implementaions, a'la the open source way. I don't know what this means. Cheers, Aaron -Sivan On 12/10/11 15:27 [email protected]<mailto:[email protected]> wrote: Hi, While V8 is definitely awesome and sharing its regexp implementation would likewise be awesome, it really isn't feasible. V8 isn't a collection of independent features, loosely coupled together like Qt is - it is a tightly integrated, highly optimised whole. You cannot simply link the V8 library and then tease out its regexp implementation. The input, output and internal parameters, the code generator and the code cache used by their regexp implementation are all expressed in terms of V8 heap primitives. This not only means that all Qt's input types - like QString - would need to be reallocated inside the V8 heap, it also means that you need to run the V8 garbage collector to clean these resources up. This in turn requires bootstrapping the rest of V8. In short, you are running a JavaScript engine. Cheers, Aaron On 12/10/2011, at 7:39 AM, ext Thiago Macieira wrote: > On Tuesday, 11 de October de 2011 19:11:02 Andre Somers wrote: >> Would it be conceptually feasible to separate V8's engine from V8 >> itself, and make V8 link against the separated out engine? Would such a >> change in V8 be accepted upstream? If so, then it would open up the >> perspective of just using V8's regexp engine, and don't load the rest of >> it if not needed... >> >> /me is just daydreaming here... > > I'm not sure. In my quick inspection into V8 about a month ago, I didn't pay > attention to the RE code. > > However, I understand that V8 automatically compiles the RE straight into > native code, which means the V8 infrastructure and assembler must be present. > At the very least, this is going to be a large duplication of code between V8- > JS and V8-RE. > > -- > Thiago Macieira - thiago (AT) macieira.info - thiago (AT) > kde.org<http://kde.org> > Software Architect - Intel Open Source Technology Center > PGP/GPG: 0x6EF45358; fingerprint: > E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 > _______________________________________________ > Qt5-feedback mailing list > [email protected]<mailto:[email protected]> > http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback _______________________________________________ Qt5-feedback mailing list [email protected]<mailto:[email protected]> http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
