1 Apr
2013
1 Apr
'13
2:55 p.m.
On Mon, Apr 1, 2013 at 6:24 PM,
There is one thing that might impact the 'warnings as errors' crowd.
There are phoenix warnings generated as a side-effect of using log.
Who owns these issues, the library or the consumer?
I think, maintainers of each library are free to choose their own policy with regard to warnings. You can contact Boost.Phoenix authors for their opinion on this, or create a Trac ticket (preferably, with a patch). Personally, I feel reluctant to maintain hard no-warnings guarantee in Boost.Log, simply because it's too tedious and most warnings on higher levels are bogus anyway and trying to avoid them only makes the code worse. I try to keep the code silent on normal levels, however.