[FFmpeg-devel] How to handle compiler warnings
Sun Feb 3 22:58:04 CET 2008
On Thu, Jan 31, 2008 at 03:28:11PM +0100, Michael Niedermayer wrote:
> On Thu, Jan 31, 2008 at 10:19:56AM +0100, Diego Biurrun wrote:
> > On Tue, Jan 29, 2008 at 11:45:15AM +0100, Diego Biurrun wrote:
> > > The topic has come up again, it's time to discuss the subject. I
> > > propose to try to avoid compiler warnings as much as possible in order
> > > to
> > >
> > > - have cleaner code,
> > > - have important warnings not be drowned out,
> > > - make FFmpeg a programming textbook.
> > >
> > > This does not include warning fixes that slow things down or obfuscate
> > > the code, but if in doubt I personally would err on the side of fixing
> > > the warning.
> > OK, we pretty much seem to have consensus about this. Should we add a
> > paragraph about warnings to the policy?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 693 bytes
Desc: not available
More information about the ffmpeg-devel