Am Mon, 14 May 2018 08:45:06 -0700
schrieb Thiago Macieira :
> ...
>
> It's a matter of perspective. As seen in this thread, in some situations
> failing to write everything is an unrecoverable situation. That is the case
> here: QDataStream cannot recover from a partial write.
>
> We could lo
On 05/14/2018 10:54 AM, interest-requ...@qt-project.org wrote:
Finally, Qt isn't used in mainframes. So mainframes are not an argument for
this discussion.
It's on LinuxOne.
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Wdf4d0ae77421_40d3_9e0e_ad0889993334/page/ClefOS
On Monday, 14 May 2018 09:17:42 PDT Roland Hughes wrote:
> > ?That is simply incorrect. It might not be how you would like it to
> > behave,
> > however it is the norm that short writes are allowed and should be handled
> > by the callee. This is the case in POSIX, the C standard library etc. I'm
>
On 05/14/2018 10:54 AM, interest-requ...@qt-project.org wrote:
On Saturday, 12 May 2018 07:11:57 PDT Roland Hughes wrote:
On 05/12/2018 08:57 AM, Thiago Macieira wrote:
I'm claiming that Qt is run 1% of the time in big-endian mode. Explain to
me why the 99% should perform the byte swap.
Beca
On 05/14/2018 10:54 AM, Thiago Macieira wrote:
On Saturday, 12 May 2018 07:18:03 PDT Roland Hughes wrote:
On 05/12/2018 08:57 AM,interest-requ...@qt-project.org wrote:
On Thursday, 10 May 2018 23:11:04 PDT alexander golks wrote:
i think it "silently" breaks here without setting error condit
On 05/14/2018 10:54 AM, Richard Moore wrote:
On Sat, 12 May 2018 at 15:45, Roland Hughes
wrote:
Any time a write comes up short, it is an error.
?That is simply incorrect. It might not be how you would like it to behave,
however it is the norm that short writes are allowed and should be han
On Monday, 14 May 2018 08:14:24 PDT Jason H wrote:
> Is there going to be some kind of serialization operator/function for CBOR?
Yes.
https://codereview.qt-project.org/107465 - QCborStreamWriter
https://codereview.qt-project.org/107466 - QCborStreamReader
https://codereview.qt-project.org/214286
On Monday, 14 May 2018 00:32:38 PDT alexander golks wrote:
> > int QDataStream::writeRawData(const char *s, int len)
> > {
> >
> > CHECK_STREAM_WRITE_PRECOND(-1)
> > int ret = dev->write(s, len);
> > if (ret != len)
> > q_status = WriteFailed;
> > return ret;
> >
> > }
>
> Sent: Saturday, May 12, 2018 at 1:06 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Interest Digest, Vol 80, Issue 8
>
> On Saturday, 12 May 2018 07:11:57 PDT Roland Hughes wrote:
> > On 05/12/2018 08:57 AM, Thiago Macieira wrote:
> > > I'm claiming that Q
2018-05-14 1:29 GMT+02:00 Thiago Macieira :
> On Sunday, 13 May 2018 09:32:23 PDT Elvis Stansvik wrote:
>> QDataStream can operate
>> fine on an QIODevice that does partial writes (like QFile).
>
> No, it cannot. If there's a failure to write, the stream is corrupt and
> unrecoverable.
Yes of cour
Am Sun, 13 May 2018 23:50:20 -0700
schrieb Thiago Macieira :
> On Sunday, 13 May 2018 23:28:47 PDT alexander golks wrote:
> > > In fact, QDataStream can't recover from any errors.
> >
> > as you've said, my origin problem is no error.
> > wouldn't it be possible for QDataStream to handle this n
11 matches
Mail list logo
