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 no-errors, too?
It already does.
int QDataStream::writeRawData(const char
Am Sun, 13 May 2018 16:29:48 -0700
schrieb 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
> unr
On Sunday, 13 May 2018 23:02:56 PDT alexander golks wrote:
> still this makes QFile unusable with QDataStream, doesn't it?
> isn't the documentation for QIODevice::writeData not correct then?
No more so than any other QIODevice. If QFile fails to write for some reason,
then QDataStream can't reco
Am Fri, 11 May 2018 08:34:09 -0700
schrieb Thiago Macieira :
> On Friday, 11 May 2018 04:08:48 PDT alexander golks wrote:
> > > It is not silent, you have the return value so you can detect when the
> > > number of written bytes is not equal to the size of the data.
> >
> > the error is 0. and
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.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
2018-05-13 18:03 GMT+02:00 Elvis Stansvik :
> 2018-05-13 14:58 GMT+02:00 william.croc...@analog.com
> :
>>
>>>
>>> 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
2018-05-13 14:58 GMT+02:00 william.croc...@analog.com
:
>
>>
>> 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
>>
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 afraid,
you'll simply have to learn to live with it - an easy solution
