[Development] Proposed API change: Change signature of QMessageHandler to use QString

Thiago Macieira thiago.macieira at intel.com
Thu Apr 12 18:05:40 CEST 2012


On quinta-feira, 12 de abril de 2012 14.41.27, kai.koehne at nokia.com wrote:
> > Maybe QChar *begin, int len?
> > 
> > Or QChar *begin, guaranteed to be NUL-terminated?
> 
> What's the advantage of having a QChar * in contrast to a QString?

To be honest, not much. I was just wondering if we could use a pre-allocated 
buffer in case we wanted to show a message in an OOM situation.

> > fromAscii() was correct in the sense of "from whatever the user used in
> > developing source code".
> 
> Just realized that nowadays fromAscii==fromLatin1. So it's really just a
> matter of taste.

Not for long. I still need to change fromAscii to be fromUtf8. Provided it 
doesn't break too much.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120412/267215a7/attachment.sig>


More information about the Development mailing list