[Development] QProperty and library coding guide

Thiago Macieira thiago.macieira at intel.com
Sun Jul 19 17:20:01 CEST 2020


On Sunday, 19 July 2020 03:51:00 PDT Oswald Buddenhagen wrote:
> - the compiler becomes intentionally belligerent, in which case an
>    override switch will be provided as well (if not instantly, then after
>    the outcry that immediately follows)

Even if that were the case, we'd need EVERYONE's code to use this switch. Not 
just when Qt is being built, where we control the options. We'd need all our 
users to use it, in their buildsystems, whichever they may be.

That's why this is not acceptable.

> <insert your brilliant idea here> 

If Peppe's idea doesn't work, then:

1. Revert the feature.
2. Write papers to add necessary functionality to C++23, like reversing a
   pointer-to-member-object back to the containing object
3. Require C++23 in Qt 7.0

double Square::_qt_property_api_width::value() const
{
    return retrieveContainer<&Square::width>(this)->d->width;
}
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products





More information about the Development mailing list