23.09.2016, 18:41, "Jason H" <jh...@gmx.com>: >> Sent: Friday, September 23, 2016 at 11:14 AM >> From: "Thiago Macieira" <thiago.macie...@intel.com> >> To: interest@qt-project.org >> Subject: Re: [Interest] Current QDataStream format documentation? >> >> On sexta-feira, 23 de setembro de 2016 17:05:26 PDT Jason H wrote: >> > > Sent: Thursday, September 22, 2016 at 10:12 PM >> > > From: "Thiago Macieira" <thiago.macie...@intel.com> >> > > To: interest@qt-project.org >> > > Subject: Re: [Interest] Current QDataStream format documentation? >> > > >> > > On sexta-feira, 23 de setembro de 2016 03:01:40 PDT Jason H wrote: >> > > > The documentation should be current. Maintaining documentation is part >> > > > os >> > > > selling the toolkit. >> > > >> > > The maintainer of QDataStream (me) disagrees. I don't like the >> versioning >> > > support in the first place, since it's an all-or-nothing. >> > >> > So the expectation is that I dig through [thousands, hundreds, dozens?] of >> > commits to find out what changed? I wouldn't even know where to start. >> >> The expectation is that you read QDataStream with QDataStream. You don't >> need >> to know what it writes, only that it can read what it writes. > > Which is great until it's writing to another device that does not implement > Qt, because it's an Arduino or similar. I don't think it's an unusual > scenario that you're using QDataStream to exchange data to a device that does > not implement Qt.
In this case you will have better result by using one of existing well-defined serialization formats -- Regards, Konstantin _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
