undefined | Better HN

0 pointsspacechild11mo ago0 comments

> That's because the default mode for compilers is to just shut up and compile this throw away code.

That's just not true. Compilers do issue certain warnings by default and they even treat some warnings as errors. See https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html

> ?? Uninitialized variables are also serious issues and also undefined behaviour.

Oh my, I meant to write "unused variables" facepalm. Uninitialized variables are of course a serious issue.

So back to my original point: you said that warnings in C are always a serious thing, but that's not really true. Warnings can range from more or less harmless to very serious. In fact, compilers recognize this issue by upgrading certain warnings to errors by default. See again my link to the GCC 14 post: https://gcc.gnu.org/gcc-14/porting_to.html.

0 pointsspacechild11mo ago0 comments

> That's because the default mode for compilers is to just shut up and compile this throw away code.

That's just not true. Compilers do issue certain warnings by default and they even treat some warnings as errors. See https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html

> ?? Uninitialized variables are also serious issues and also undefined behaviour.

Oh my, I meant to write "unused variables" facepalm. Uninitialized variables are of course a serious issue.

0 comments

3 comments · 1 top-level

17186274401mo ago· 2 in thread

> That's just not true. Compilers do issue certain warnings by default and they even treat some warnings as errors.

Because some warnings are just believed to be more serious, than others.

> In fact, compilers recognize this issue by upgrading certain warnings to errors by default.

Which I interpret as a culture shift, due to people complaining about it and also because the contemporary meaning and expectation of warnings for programming languages has shifted.

spacechild1OP1mo ago

> Because some warnings are just believed to be more serious, than others.

Yes, that is my entire point. For some reason you were arguing against it.

17186274401mo ago

I didn't intend to.

> Also, let's not forget that implicit casts between unrelated pointer types is only a warning in C.

I intended to argue against the "only a warning", because the meaning of a warning in C is something very serious. That is different from more modern languages, who may use this to inform you that you are no longer writing idiomatic code. Of course there are also exceptions, that you often need to enable explicitly. But the fact that something is a warning in C, doesn't mean it's nothing serious, quite the opposite. That's my point.

1 more reply

j / k navigate · click thread line to collapse