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?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?
Cheers, -- 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
