On 4/23/20 10:55 AM, Simon Hausmann wrote:
So take for example this function in QIconEngine:virtual QList<QSize> availableSizes(QIcon::Mode mode = Icon::Normal, QIcon::State state = QIcon::Off) const;If we change that to QVector, we require our users to clutter their code base with #ifdefs. If we keep it with QList but use QVector in all non-virtual functions, then we create a less consistent API.
Why do you say "we require"? What kind of user code would break? Thanks, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | 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: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
