|
![](/i/fill.gif) |
>> You only get 710? :) Most of them are precision warnings
>Ron, it is nearly useless to try to remove this because it all is a result
>of the macro DBL
DBL x = 2.0;
becomes
DBL x = (DBL) 2.0;
Is there anything unreasonable or dangerous about doing this?
I think it is worth keeping the MS compiler quiet, because sometimes
things like signed/unsigned, unused, uninitialised variable, actually
help solve problems.
Has anyone run POV through Purify, or Bounds Checker?
Post a reply to this message
|
![](/i/fill.gif) |