• Luca Boccassi's avatar
    Problem: no automated way to enforce C++98 compatibility · 1402f772
    Luca Boccassi authored
    Solution: if the compiler supports it, pass C++98-compat flags.
    Currently Clang supports this flag but GCC does not.
    
    Add a new flag to enable it, as building with C++98-compat but also
    with -std=gnu++11 will cause a lot of warnings due to the backward
    compat ifdefs.
    
    Add a CI job to run it and ensure we don't break compatibility.
    1402f772
Name
Last commit
Last update
.github Loading commit data...
RELICENSE Loading commit data...
builds Loading commit data...
doc Loading commit data...
external Loading commit data...
include Loading commit data...
m4 Loading commit data...
packaging Loading commit data...
perf Loading commit data...
src Loading commit data...
tests Loading commit data...
tools Loading commit data...
unittests Loading commit data...
.clang-format Loading commit data...
.clang-tidy Loading commit data...
.gitignore Loading commit data...
.hgeol Loading commit data...
.mailmap Loading commit data...
.travis.yml Loading commit data...
AUTHORS Loading commit data...
CMakeLists.txt Loading commit data...
COPYING Loading commit data...
COPYING.LESSER Loading commit data...
Dockerfile Loading commit data...
Doxygen.cfg Loading commit data...
INSTALL Loading commit data...
Jenkinsfile Loading commit data...
Makefile.am Loading commit data...
NEWS Loading commit data...
README.cygwin.md Loading commit data...
README.doxygen.md Loading commit data...
README.md Loading commit data...
acinclude.m4 Loading commit data...
appveyor.yml Loading commit data...
autogen.sh Loading commit data...
branding.bmp Loading commit data...
ci_build.sh Loading commit data...
ci_deploy.sh Loading commit data...
configure.ac Loading commit data...
installer.ico Loading commit data...
version.sh Loading commit data...