[Development] QLibraryInfo::path(): to deprecate or not to deprecate?
Thiago Macieira
thiago.macieira at intel.com
Sun Jul 26 20:09:20 CEST 2026
In favour of QLibraryInfo::paths()
https://codereview.qt-project.org/c/qt/qtbase/+/744726
The correct thing to do is to deprecate, and force everyone who is using it to
adjust to having more than one path. In a lot of cases, it's already used in a
loop, so the fix is simple. In others, it's the right thing to do. And in the
rest, it documents in the code that you're taking the first and ignoring the
remainder, which is what path() does.
But it produces a lot of warnings in examples and tests.
Do we want this?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Principal Engineer - Intel DCG - Platform & Sys. Eng.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5176 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20260726/c7319b80/attachment.bin>
More information about the Development
mailing list