Re: Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests

[lilypond]

Updates:
        Labels: -Patch-new Patch-needs_work

Comment #8 on issue 814 by address@hidden: warning-as-error should  
be enabled when compiling the regtests
http://code.google.com/p/lilypond/issues/detail?id=814

Actually, the check for warning-as-error should be done in just one place,  
and that's warn.cc. Everywhere else you would just work with a normal  
warning, but the logging backend then decides that a warning should be  
treated as an error..
Seems like I mixed something up here. The check was never in warn.cc, so I  
shouldn't remove it from input.cc.

The only proper solution is to add the check somehow to warn.cc, but the  
problem is in flower/ we don't have access to scheme options. On the other  
hand, if we don't have the check in warn.cc, we'll miss several warnings.

Any ideas how to get the warning-as-error setting from warn.cc?