> i hadn't thought about it before. why aren't FVTw on by default? > is this a historical accident?
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. russ
