Re: Issue 1477 in lilypond: suppress output for expected warnings

[lilypond]

Comment #8 on issue 1477 by address@hidden: suppress output for expected  
warnings
http://code.google.com/p/lilypond/issues/detail?id=1477

'the regtest comparison is quite verbose, and generally contains tons of  
false "warnings"'

Warnings are part of the functionality of the program, so they should be  
tested, rather than papered over.

If you find that the regtest comparison generates false, diffs, can we  
adopt an issue to fix those false diffs instead?

When running 'make test', most if not all warning output is diverted into  
log files anyway, so there isn't really a way to see those warnings; what  
are you complaining of exactly?

To be more clear: I am proposing that the regtest is taken out of the scope  
of whatever this issue is about.  I am fine with whatever you do to the  
docs, although I remain skeptical that you can build an effective warning  
suppression system without polluting the C++ code with lots of extra  
infrastructure.