> i think you could make that argument, but > it's probably not worth changing now. > a large part of the problem is that most > of those flags (not w) turn on errors, not > warnings, so making them the default > would reject once-valid c programs. > > this is one thing that we tried to get right > in go - 8g has no warnings, only errors, > as far as possible they're mandated by > the language spec, and there are no options > to turn them off. as rob likes to say, > if it's worth warning about, it's worth fixing.
the tradition of c is that old programs may no longer compile without options. i wonder how much of 1e would currently compile. perhaps this is a bad tradition, but it's what we've got. and i think that rob's comment may equally apply to old code and old languages. - erik
