[FFmpeg-devel] How to handle compiler warnings
Thu Jan 31 15:28:11 CET 2008
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?
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When the tyrant has disposed of foreign enemies by conquest or treaty, and
there is nothing more to fear from them, then he is always stirring up
some war or other, in order that the people may require a leader. -- Plato
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel