On Wednesday, 28 de September de 2011 09:39:13 [email protected] wrote: > > I don't see why JSON must be restricted to QtNetwork. It's very > > valuable as a simple, yet versatile in-house data specification > > format. For example, I've already used it as an input format in a > > simple C++ code generator. Like Girish said, an implementation can be > > done in a couple hundred lines, so not something I'd like to pull in > > complete QtNetwork for. > > Is there any reason not to have json as a standalone library then?
Other than the reason you found below, I don't think there's any.
> Arguments against would be if the DLL overhead is too high compared to the
> code / data sizes. (e.g. the 4 bytes of static data rounded up to a 4k page
> per process problem)
You used a Symbian symptom to the problem of having too many libraries, but
other OSes have similar issues. On Linux, the symbol search complexity is
O(n*m), which depends on the number of libraries loaded (one hashing table per
library with a bad hashing function).
If this codebase turns out to be small, flexible and fast, I'd vote for having
it in QtCore. We have QXmlStreamReader and Writer there for a reason, moved
out of QtXml.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
