Hi,

Warnings are important and should be kept. This is actually the first question I ask whenever a customer is confronted to ill CAD tool behavior (whether I actually coded it or not): "did you read (and hopefully understood) all warnings?"

Problem is, your issue seems to be of social engineering kind (i.e., fellow programmers are dead set against warnings) so I would first debunk their cons one by one (benchmarking is IMHO a very good idea) then quiet most or every warning. Of course, you can end up locally inserting 'no warnings' pragma into any dodgy code block you would not have time to properly analyze or refactor.

My 2 cents anyway...

Cheers,

Xavier