> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > Timo Rothenpieler > Sent: Monday, 6 September 2021 23:13 > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] Code Style and Diagnostic Issues > > On 06.09.2021 22:17, Soft Works wrote: > > Hi, > > > > I wonder whether there’s a commonly agreed set of code issues that > should > > be checked for, e.g. via clang-diagnostic? > > > > This would help with a number of questions I’m wondering about and > for > > which it is not possible to derive rules from the existing code > base. > > For example: should constant local variables be marked as const, > should > > pointer casts be made explicit, etc. ? > > > > softworkz > > We're using Coverity for regular static analysis. > I think Michael can set you up if you want access.
I'd rather be interested in the ruleset being used. Then I could translate it to clang-diagnostic rules which allow me to see issues right in the IDE - at least basic ones, probably Coverity goes way beyond that.. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".