On Monday, 17 de October de 2011 19:33:07 Oswald Buddenhagen wrote: > On Mon, Oct 17, 2011 at 02:55:53PM +0200, Knoll Lars (Nokia-MP-Qt/Oslo) wrote: > > Why would we want to add a wrapper for char's? > > why again do we have a wrapper for ushort called QChar? after all, some > global functions operating on ushort would do. ;)
What functions do you want to have on QByte?
> one of the advantages of a unified codebase would be making an end to
> qbytearray constantly lagging behind qstring in api for no good reason.
The good reason is that it's not a string. It's a sequence of arbitrary bytes
which are not a string.
> > QString also has Unicode methods, which QByteArray doesn't.
>
> my remark about data() alone is enough to see that there have to be
> specialized subclasses made from the template. and obviously, the
> qstring-specific functionality would stay in qstring as ever.
>
> > Unless you're suggesting we make it possible to use UTF-8 QStrings...
>
> if you mean hybrid strings (bytearray + codec pointer), that's certainly
> an interesting topic, but i'm not too concerned about that now.
If you're not suggesting that for now, I don't get what the point of adding
this common code.
What methods are you missing in QByteArray that QString has?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
