> > We're not going to get them all, that's for sure. On one hand, the V8 > engine > is very performant, works on UTF-16 and avoids code duplication, but it > increases the footprint and restricts the platforms addressed. On the > other, > PCRE is performant too, works almost everywhere and is small, but requires > UTF-8←→UTF-16 conversion. > > I believe the standard WebKit has a PCRE engine inside, modified to work on > UTF-16. That's also an option, but it is code duplication and causes us to > have to maintain it. >
PCRE seems to be the better choice, no dependency on V8, and small footprint. furthermore you have the possibility to use it on UTF-16. However I do not understand why you have to maintain it because it is part of webkit. > So maybe the solution is a hybrid: dlopen V8 where it is available, fall > back > to libpcre otherwise. And crash if none is found. That means using regexps > will cause a library to be loaded, one that can be as big as V8. > I would not do that, I would choose only PCRE and have the same behavior on all platforms Additionally V8 is a so huge dependency that it should be avoided for standard bricks like regexp. Best regards, Sylvain
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
