News for hackers. Stuff that matters.

A comment on What Every C Programmer Should Know About Undefined Behavior (2011). Parent comment

Re:What Every C Programmer Should Know About Undefined Behav... by mattkrause on Thursday January 05, 2017 @09:03AM (#13327130)
The "confusing indentation" warning can be useful. For example, it would have flagged

  if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)

      goto fail;

      goto fail;
Does any compiler try to indicate the severity of each warning. For example, using the value from an uninitialized variable is labeled as somehow "worse" than code-quality warnings like indentation or bare assignments inside conditionals?
[ Parent | on HN ]

There are no comments on this comment yet.