13 Aug
2007
13 Aug
'07
10:57 a.m.
Andreas Huber wrote:
Since I believe that *all* users who care about warnings will *want* to disable these in their code anyway, I think the most user-friendly approach is to permanently disable them in the library header.
Not necessarily correct. I care about warnings (most of the time) but don't disable 4511/4512 and don't get them, except from third-party code.