Re: [Interest] Current QDataStream format documentation?

On sábado, 24 de setembro de 2016 20:39:48 PDT Thiago Macieira wrote: > Network IPv4IPv6x The x is a typo. There's no such thing as IPv6x different from IPv6 that you may not have yet heard of. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel

Re: [Interest] Current QDataStream format documentation?

On domingo, 25 de setembro de 2016 01:38:12 PDT Konstantin Tokarev wrote: > Hopefully there are lots of JSON-like (as well as non-JSON-like) binary > formats that have already been implemented for C++ Like I said in the other email, CBOR. https://github.com/01org/tinycbor This library compiles

Re: [Interest] Current QDataStream format documentation?

On sábado, 24 de setembro de 2016 23:50:33 PDT Giuseppe D'Angelo wrote: > > The decision is like this: it starts equal to the last release's number. > > If > > you modify one of the operator<<, you bump the number. > > But "you" who? The release manager at release time? Whoever submits a > change

Re: [Interest] Current QDataStream format documentation?

On domingo, 25 de setembro de 2016 14:31:48 PDT Ch'Gans wrote: > "Gigantic"? That's sounds very much speculative... They run HTTP > servers over TCP/IP on arduino (just a random example). > > Yes JSON will add some overhead, as Thiago pointed out, CBOR [1] can > be an alternative. If you're

Re: [Interest] Current QDataStream format documentation?

On 25 September 2016 at 10:38, Giuseppe D'Angelo wrote: > Hi, > > Il 24/09/2016 02:50, Ch'Gans ha scritto: >> Adding my 2 cents, I haven't use QDataStream stream much, yet i'm very >> well aware of this restriction. I think the documentation is very >> explicit about

Re: [Interest] Current QDataStream format documentation?

25.09.2016, 00:39, "Giuseppe D'Angelo" : > Hi, > > Il 24/09/2016 02:50, Ch'Gans ha scritto: >>  Adding my 2 cents, I haven't use QDataStream stream much, yet i'm very >>  well aware of this restriction. I think the documentation is very >>  explicit about this. And

Re: [Interest] Current QDataStream format documentation?

Il 24/09/2016 02:22, Thiago Macieira ha scritto: > On sexta-feira, 23 de setembro de 2016 19:05:28 PDT Giuseppe D'Angelo wrote: >> Il 23/09/2016 17:14, Thiago Macieira ha scritto: >>> The expectation is that you read QDataStream with QDataStream. You don't >>> need to know what it writes, only

Re: [Interest] Current QDataStream format documentation?

Hi, Il 24/09/2016 02:50, Ch'Gans ha scritto: > Adding my 2 cents, I haven't use QDataStream stream much, yet i'm very > well aware of this restriction. I think the documentation is very > explicit about this. And that might be the reason i haven't use it > much. I'm actually arguing that there's

Re: [Interest] Optimizations in debug configuration

On Sat, Sep 24, 2016 at 9:00 AM, Thiago Macieira wrote: > It probably comes from the environment variables of the machine that built > the > package. Indeed. Using my own Qt build resolves the issue (installed mkspec doesn't contain the mentioned line either). Thanks

Re: [Interest] menu item reuse and reparenting (dynamically populated submenus remaining empty/disabled on OS X)

René J.V. Bertin wrote: Hello, I've realised that the symptom described below is in fact a new face of the 5.4 and 5.5 Mac issue where adding QMenus, QActions and/or QActionWidgets to more than only a native QMenuBar menu would lead to continuous error messages. In short, it's caused by the

Re: [Interest] Optimizations in debug configuration

On sábado, 24 de setembro de 2016 04:25:05 PDT Konstantin Shegunov wrote: > Curiously enough, that line isn't present in the Qt's source for the same > version I have from git. Is it possible it was inserted automatically on > install, or whatever process is used for packaging the binaries for