On Monday, 3 December 2018 02:02:31 PST Giuseppe D'Angelo via Development wrote: > Il 03/12/18 00:01, Thiago Macieira ha scritto: > >> Has anyone actually tried changing size_type to a 64bit datatype, and > >> checking how many warnings start appearing in user code? (E.g. just try > >> with QString, QList, QVector; and build Creator, or some KDE libs). I've > >> got the gut feeling that it will be an absolutely gigantic number, > >> especially on Windows... > > > > Not yet. Yes, it will be a huge number. > > Which compels the questions: > > 1) is it worth it?
I think so, but we can document that going above 2 GB is experimental and not well tested, since it will be difficult for us to test. But getting the containers and QString and QByteArray done should be doable by the 6.0 release. > 2) should we offer users some way (configure time switch, template > parameter, ...) to keep int-based indexes and avoid all these warnings > while they fix their code to use a ssize_t-like index? No. There will be no warnings. We'll fix the all before the release. The question is only if we've identified all places that need to be fixed, those that don't produce a warning. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
