Florian Fainelli schrieb:
Le jeudi 25 octobre 2007, Manuel Lauss a écrit :
then where's the harm in leaving it in? It only forces you to think twice
(or apply tons of casts) when working with the au1x code.
II could argue the same way, why not :p ?
Hehe ;)
If your code has warning, you are very likely not to like the compiler stop on
it, but rather warn. Also if there are casts or any special conversion,
sparse checking will do a better job as far as I can tell.
I tripped over it once or twice; but in the end I don't really whether
this stays or goes (not that it matters anyway)
Thanks,
Manuel Lauss
