This Wiki page is a bit outdated; for example there are a few compiler warnings on old compilers in combination with specific boost versions. That said we should check warnings for Travis (and the Windows CI ..) and especially our production builds.
I think a "coding standard" boils down to: - adapt your naming convention to what's already present in the code base - use clang-format for formatting - include what you use for everything else someone will flag it on the pull request. HTH, Daniel J H On Sun, Sep 10, 2017 at 9:01 PM, Mateusz Loskot <[email protected]> wrote: > Hi, > > Is this policy still respected? > > "Treat Compiler Warning as Errors!" [1] > > [1] https://github.com/Project-OSRM/osrm-backend/wiki/Coding-Standards > > Best regards, > -- > Mateusz Loskot, http://mateusz.loskot.net > > _______________________________________________ > OSRM-talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/osrm-talk >
_______________________________________________ OSRM-talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/osrm-talk
