On Saturday, 3 de December de 2011 23.39.57, Francesco Riosa wrote:
reading these two blogs:
http://blog.rburchell.com/2011/12/why-i-avoid-qregexp-in-qt-4-and-so.html
http://blogs.kde.org/node/4510 (Regexp library benchmarks...)
I've learned of the TRE library
2011/11/23 Thiago Macieira thi...@kde.org:
We don't even have to mark this one deprecated. If the new engine's API is
compatible, it could be used for both.
well doesn't that depend on how complete you want SC to be?
QRegExp uses different syntax than pretty much every other RE engine,
On 11/23/11 3:30 PM, ext Thiago Macieira thi...@kde.org wrote:
On Monday, 21 de November de 2011 21:25:07 lars.kn...@nokia.com wrote:
One interesting piece will be how we continue with this. We will most
likely need one regexp engine in QtCore (as regexp's are being used
internally in Qt in a
On Tuesday, 22 de November de 2011 09.58.02, lars.kn...@nokia.com wrote:
A IMO better solution would be to have a repository called e.g. qtsupport
(KDE had something similar for quite a while) that contains copies to
these 3rd party libraries for convenience.
I'd prefer that too.
And to keep
On Friday, November 11, 2011 13:01:55 Zoltán Herczeg wrote:
Hi Qt Devs,
I am Zoltan Herczeg, a PCRE and a QtWebKit developer. Stephen Kelly told me
that Qt would like to replace the QRegExp engine with another regex engine
(http://thread.gmane.org/gmane.comp.lib.qt.qt5-feedback/1524/), and he
On 11/21/11 6:29 PM, ext Thiago Macieira thi...@kde.org wrote:
On Monday, 21 de November de 2011 15.45.49, Giuseppe D'Angelo wrote:
But first: do we all (esp. Thiago, Lars) agree to use the UTF-8
version for now (and pay for the pattern/subject string/offsets
conversions) and then write and
Hi Qt Devs,
I am Zoltan Herczeg, a PCRE and a QtWebKit developer. Stephen Kelly told me
that Qt would like to replace the QRegExp engine with another regex engine
(http://thread.gmane.org/gmane.comp.lib.qt.qt5-feedback/1524/), and he _really_
encouraged me to tell you that we consider adding
Hi Zoltan,
Great to hear from you. UTF16 support would be a basic requirement for us
using it in Qt. We don't really need wchar_t support though.
Our main issue seem to be timing then. We currently have the opportunity
of changing API to some extend before we freeze down things for Qt 5
again.
hi,
On Fri, Nov 11, 2011 at 1:10 PM, lars.kn...@nokia.com wrote:
Our main issue seem to be timing then. We currently have the opportunity
of changing API to some extend before we freeze down things for Qt 5
again. Thus we'd need something relatively soon to be able to use it for
5.0.
hmm,
