On Thursday, 10 July 2025 06:01:25 Pacific Daylight Time Fabian Kosmale via Development wrote: > I really don't like "undocumented API can change", especially not for > members. Using such a member is one tab completion away > > I'm willing to make some amends (function which can't be used without > also using private API, like a function taking an instance of a private > class), but I think the general guide line should IMHO be: Use the > normal deprecation workflow for them.
The interesting thing about this case is that it is both. QArrayData and QTypedArrayData are not documented, but are otherwise public classes. I wouldn't be surprised if someone found them and decided to use them, or QADP, for the very purpose they were created. Manipulating the reference count may be uncommon, but it might happen. And yet the use inside of Qt Creator got to a QString's QArrayData through a clearly-marked private API. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel Platform & System Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
