[asterisk-scf-dev] building asterisk-scf part2

[David M. Lee]

On Oct 22, 2011, at 2:31 PM, Paul Belanger wrote:

> Is there a simple way to allow the warnings?  I know the proper fix is to actually fix them, but I have some free time ATM and wanted to see if I could get a build to work.

I've been thinking about this.  

This warning is in the code generated by slice2cpp (which is why it's not just a simple fix).  I wonder if treating warnings as errors for generated code is worthwhile.

Many warnings indicate potential problems resulting from people maintaining the code instead of problems with the code itself.  But since the code is generated by a program, who cares if it's maintainable?  Does is matter if generated code has unused variables?  Or unused parameters?

I propose that we either disable warnings for the compiling of generated .cpp files, or at least disable the warnings that indicate code maintenance problems.

Thoughts?

-- 
David M. Lee
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at:  www.digium.com  & www.asterisk.org