apoenitz at t-online.de
Fri Sep 20 00:11:54 CEST 2019
On Thu, Sep 19, 2019 at 11:37:14PM +0200, Giuseppe D'Angelo wrote:
> Il 19/09/19 21:53, Kyle Edwards ha scritto:
> > As a generalization of this, perhaps Qt could introduce something like
> > a Q_CONSTEXPR macro, which does what we expect on platforms that
> > support it, and compiles to nothing on Integrity.
> It's already in Qt, and used:
> > https://code.woboq.org/qt5/qtbase/src/corelib/tools/qarraydata.h.html#_M/Q_ARRAY_LITERAL_IMPL
> Revocation of Q_CONSTEXPR is not so simple, as it's a source incompatible
It's a fairly safe assumption that given a choice of a SiC change and completely
dropping a platform most users of that platform would prefer the SiC change.
> (It's one of the reasons why stdlib implementors are not allowed to
> plaster constexpr unless the Standard says so.) It might work in the case in
> question, for which I've already asked for help twice in a few months
> (again: I don't have any access to INTEGRITY). It will just not work for
> other cases where you do want a constant expression, bringing us back to
> square one.
The context was dropping support for INTEGRITY, not "other cases".
More information about the Development