(Jumping in a rather old thread...) Il 02/11/18 09:52, Lars Knoll ha scritto:
The size mismatch warnings users will get in Qt 6 are IMO not a huge issue. The narrowing to a smaller size does not break compatibility, as long as no container overflows in size (which it couldn’t with code based on Qt 5).So my vote actually goes for option 4. We introduce a central type that’s int in Qt 5, qsizetype in Qt 6, and start using it. That allows us to introduce it then class by class and fix any issues we find around it.
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...
Thanks, -- Giuseppe D'Angelo | [email protected] | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: Firma crittografica S/MIME
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
