diff options
author | Kevin Funk <kfunk@kde.org> | 2016-12-29 12:23:20 +0100 |
---|---|---|
committer | Kevin Funk <kfunk@kde.org> | 2017-01-16 08:46:43 +0100 |
commit | a5f3a76e14799c68b5e8f74e375baa5f6f6ab4dc (patch) | |
tree | 9d7ddcf483386c471fcf09aaea25cf7298d28256 /tests/GenerateSipBindings/cpplib.cpp | |
parent | 01f52b2b03f9e2050cc47ba58f48948ac29d1d77 (diff) | |
download | extra-cmake-modules-a5f3a76e14799c68b5e8f74e375baa5f6f6ab4dc.tar.gz extra-cmake-modules-a5f3a76e14799c68b5e8f74e375baa5f6f6ab4dc.tar.bz2 |
Pass -fno-operator-names when supported
Summary:
Disables alternative tokens for &&, ||, etc.. They're are not supported
by MSVC out of the box, thus using them will limit the portability of
the code. There *are* options to make alternative tokens available under
MSVC [1], but I think we shouldn't promote the usage of them.
From the GCC documentation:
-fno-operator-names: Do not treat the operator name keywords and,
bitand, bitor, compl, not, or and xor as synonyms as keywords.
[1] http://stackoverflow.com/questions/555505/when-were-the-and-and-or-alternative-tokens-introduced-in-c
Reviewers: #frameworks, #buildsystem, ivan
Reviewed By: ivan
Subscribers: rakuco, elvisangelaccio
Differential Revision: https://phabricator.kde.org/D3850
Diffstat (limited to 'tests/GenerateSipBindings/cpplib.cpp')
0 files changed, 0 insertions, 0 deletions