My recommendation with clang-tidy is to start with all warnings disabled. Then pick one that looks to be more likely to have constructive warnings. Work on just those. Then you can progressively add them. And don't try to deal with warnings for anything involving swig.
On Thu, Jun 10, 2021 at 12:34 PM Andrew C Aitchison <and...@aitchison.me.uk> wrote: > > I've discovered clang-tidy and am letting it loose on my gdal drives. > It is finding bugs and teaching me a lot about modern C++ > but as well as 100k+ bugs it found but did not report in "non-user code" > it reports problems where I have used macros from the GDAL/CPL headers. > > I will report or submit patches once I understand these issues; > in the mean time, are there any clang-tidy configs for gdal ? > > I have read and will reread > > https://erouault.blogspot.com/2016/01/software-quality-improvements-in-gdal.html > > Thanks, > > -- > Andrew C. Aitchison Kendal, UK > and...@aitchison.me.uk > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
