пн, 8 июл. 2019 г., 5:44 Thiago Macieira <[email protected]>:
> 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 > true > > vector of bytes now, without breaking lots of the user code, but that > could > > 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 either ;) > The question is whether the Latin1 methods (toUpper(), toLower() and the > free > 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 > [email protected] > https://lists.qt-project.org/listinfo/development Konstantin
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
