[Development] Replace QtXml backend

Konstantin Tokarev annulen at yandex.ru
Fri Jul 31 13:16:19 CEST 2015

31.07.2015, 10:43, "Sylvain Pointeau" <sylvain.pointeau at gmail.com>:
> On Tue, Jul 28, 2015 at 9:51 AM, Gerhard Scheikl <g.scheikl at avibit.com> wrote:
>> I found a nice image on stackoverflow:
>> http://stackoverflow.com/questions/9387610/what-xml-parser-should-i-use-in-c
>> If it is true, then our choice would be xerces because libxml2 doesn't have an
>> exact DOM/SAX API compliance.
> my opinion is that libxml is the best xml library, it is everywhere and it is very fast. I used libxml multiple times to parse big files, and this is just the best library for xml / xslt
> I personally don't care so much for the exact DOM/SAX API compliance, and furthermore this problem disappears because you implement a Qt API on top.

I use pugixml. It's lightning fast because it makes no string copies and doesn't convert input to UTF16 (unlike Qt's parsers)


More information about the Development mailing list