Hi all,

I see a tendency that compiler warnings get casted away.
The problem is, that these castings make your compiler 
happy, but there is a high potential that this only covers
BUGS. Everytime someone will cast away compiler warnings
he should back up his change with an assertion!

For example, casting an unsigned to a signed int:

        assert(my_unsinged <= INT_MAX);
        my_signed = (int)my_unsigned;

Also, don't get into the habit of becoming a slave
of your compiler.

If there are ambiguities, try to solve them without castings.


Ciao Robert


--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Reply via email to