aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/jsruntime/qv4functionobject.cpp
diff options
context:
space:
mode:
authorLuca Di Sera <luca.disera@qt.io>2022-10-11 10:38:04 +0200
committerLuca Di Sera <luca.disera@qt.io>2022-10-13 10:55:23 +0200
commitbece86c06afd9f32af9ac4ed81c994b73fcf9ab4 (patch)
treeb58d2c39b61c3fc4187ebd7d66303d5b040affe6 /src/qml/jsruntime/qv4functionobject.cpp
parent49b9f1f1e85ce9aee960b1384fb542daacd8b7a7 (diff)
Replace usages of Q_CLANG_QDOC with Q_QDOC
To allow the user to customize the C++ code that QDoc sees, so as to be able to work-around some limitations on QDoc itself, QDoc defines two symbols: Q_QDOC and Q_CLANG_QDOC, both of which are "true" during an entire execution of QDoc. At a certain point in time, QDoc allowed the user the choice between a custom C++ parser and a Clang based one. The Q_QDOC symbol would always be defined while the Q_CLANG_QDOC symbol would be defined only when the Clang based parser was chosen. In more recent times, QDoc always uses a Clang based parser, such that both Q_CLANG_QDOC and Q_QDOC are always defined, making them equivalent. To avoid using different symbols, and the possible confusion and fragmentation that derives from it, all usages of Q_CLANG_QDOC are now replaced by the equivalent usages of Q_QDOC. Change-Id: I25a2fe3b870281b336d5eca1f887940a7961dc31 Reviewed-by: Kai Koehne <kai.koehne@qt.io> Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Diffstat (limited to 'src/qml/jsruntime/qv4functionobject.cpp')
0 files changed, 0 insertions, 0 deletions