Re: [9fans] comments on c compiler flags

Re: [9fans] comments on c compiler flags

[erik quanstrom]

On Tue Dec 22 00:20:35 EST 2009, lucio@proxima.alt.za wrote:
> > i hadn't thought about it before.  why aren't FVTw on by default?
> > is this a historical accident?
>
> They are, in /sys/src/mkfile.proto.  Is that really such a burden?

on the other hand, it is exactly code compiled by hand that is most
in need of these flags.  and why should i have to look at
"8c -FVTw yuk.c"?  flags are supposed to be non-defaults and should
stand out.  i'll admit i just ignore cflags.  it's hard to notice if they're
wrong.

- erik

Re: [9fans] comments on c compiler flags

[Russ Cox]

> the tradition of c is that old programs may
> no longer compile without options.

that's not the tradition i've observed.

Re: [9fans] comments on c compiler flags

[erik quanstrom]

> 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

Re: [9fans] comments on c compiler flags

[Russ Cox]

> 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

Re: [9fans] comments on c compiler flags

[lucio]

> i hadn't thought about it before.  why aren't FVTw on by default?
> is this a historical accident?

They are, in /sys/src/mkfile.proto.  Is that really such a burden?

++L

[9fans] comments on c compiler flags

[erik quanstrom]

i got this response when pointing out the standard flags to
?c:

> Thanks!  It is crazy, I think, that folks should have to work
> so hard to get help from the compiler.  It should be an option
> to turn those helpful features off, especially since turning
> them off only makes sense for non-interactive use, [...]

i hadn't thought about it before.  why aren't FVTw on by default?
is this a historical accident?

- erik