> > 'warnings' fixes will be wrong and hide bogus code), making -Wall a goal > > causes people to cover up bad code with bad casts and such. > > > > '-Wall' is *NOT* a good design goal. > > Fixing warnings with bad casts is a problem, sure, but asking people > to write code without casts (if possible) that will compile cleanly with > -Wall is a reasonable thing to ask IMO.
Agreed. But most of the new code written does indeed compile with -Wall. It's the code we've 'inherited' that doesn't. > In my experience, the resulting > code tends to be more portable across architectures with different > pointer/long sizes and endian-ness. This is where I disagree. Too often people cast away the bugs and end up with overflow and sign problems. Nate To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
