>:: Please check that your code compiles and works ok before checking it in
>:: to the CVS ...
>::
>That doesn't help fully to solve the problem. Compiler and runtime libs are
>different. So the check can only be done for one (or two) compilers.
Still, it's not fun when certain files fail to compile because of silly
errors (like conflicting prototypes). ;)
>Currently my aim is, that the program is compilable with:
> gcc 2.95.2
> g++ 2.95.2
I run gcc 2.95.(3) and SAS/C (the latter is usually much more helpful on
warnings, and still much more forgiving on "errors")...
>:: Also it would be nice if you cast types that don't match the functions
>:: types into the correct one
>Casting is a bad thing. Correct the reason for the casting, not the warning
>(or the error in C++) itself. See Ada Rationale. It is Ada related, but the
>reasons are the same for every procedural language like C, Pascal, Ada, ...
Ofcos, as I said, the best thing is to use the correct one to begin with, but
if that isn't possible, atleast cast the value into the correct one.
- CISC
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
