[Development] Another integer typedef OR how to prepare for 64-bit in Qt 5

[Adam Light]

On Mon, Dec 3, 2018 at 11:02 PM Thiago Macieira <thiago.macieira at intel.com>
wrote:

> On Monday, 3 December 2018 11:43:17 PST André Pönitz wrote:
> > > 1) is it worth it?
> >
> > No.
> >
> > It's really rare to need a container of that size in a Qt context,
> > and if one does, there's always std:: containers - which are likely
> > to be used at sizes much smaller than INT_MAX anyways.
>
> It may have been in the past, but I don't think we can honestly say it
> will
> continue so in the future. As a simple example, someone may want to load a
> file larger than 2 GB via QIODevice::readAll(). It's probably a stupid
> idea to
> do that, but with a fast SSD that operation could complete in 10 seconds
> or
> less.
>
> Asking users to use std:: containers is not sufficient if we don't use
> them
> ourselves. How would the case above return a QByteArray with more than 2
> GB?
>
>
 Another place where this can be a problem is QMimeData, which uses a
QByteArray. We'd like for our application to be able to read/write >2GB
from/to the clipboard, but that's not currently possible. Reimplementing
all clipboard handling ourselves on two platforms would be a lot of work
and using std:: containers with Qt's clipboard API isn't an option.

Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20181204/b7736adc/attachment.html>