RG <[email protected]> writes: > In article <[email protected]>, > Seebs <[email protected]> wrote: > >> On 2010-09-30, RG <[email protected]> wrote: >> > You can't have it both ways. Either I am calling it incorrectly, in >> > which case I should get a compiler error, >> >> You get a warning if you ask for it. If you choose to run without all >> the type checking on, that's your problem. > > My example compiles with no warnings under gcc -Wall.
IIRC, -Wall is not reall ALL. Try with: gcc -Wall -Wextra -Werror I would still argue that should be the default, and if really there was a need, there could be options to disable some warning, or to have some errors be warnings... -- __Pascal Bourguignon__ http://www.informatimago.com/ -- http://mail.python.org/mailman/listinfo/python-list
