[Development] Oslo, we have a problem</apollo 13> [char8_t]
ritt.ks at gmail.com
Mon Jul 8 09:38:28 CEST 2019
пн, 8 июл. 2019 г., 5:44 Thiago Macieira <thiago.macieira at intel.com>:
> On Sunday, 7 July 2019 23:26:40 -03 Konstantin Ritt wrote:
> > As we have string views now, I'd vote for deprecating the string
> > manipulation methods in QByteArray. I doubt we could make QByteArray a
> > vector of bytes now, without breaking lots of the user code, but that
> > be a good first step.
> We don't have any good 8-bit string manipulation functions outside of
> QByteArray. They stay.
We don't have any good 8-bit string manipulation functions in QByteArray
> The question is whether the Latin1 methods (toUpper(), toLower() and the
> function qstricmp) should be moved or removed. Those would work really
> well in
> QLatin1String, but QLatin1String is a view, since it doesn't own the data.
> QLatin1String::toUpper() could return a QByteArray...
Perhaps there is a particular reason for the user to manipulate binary data
as if it were a string? So give him that string, QString.
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel System Software Products
> Development mailing list
> Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development