News for hackers. Stuff that matters.
Re:The Development of the C Language by pjmlp on Thursday August 31, 2017 @01:24AM (#15138333)
"Although the first edition of K&R described most of the rules that brought C's type structure to its present form, many programs written in the older, more relaxed style persisted, and so did compilers that tolerated it. To encourage people to pay more attention to the official language rules, to detect legal but suspicious constructions, and to help find interface mismatches undetectable with simple mechanisms for separate compilation, Steve Johnson adapted his pcc compiler to produce lint [Johnson 79b], which scanned a set of files and remarked on dubious constructions."

Yet it took up all these years until clang for anyone to start taking static analysis seriously in C, and even now many still ignore it.

Re:The Development of the C Language by EliRivers on Thursday August 31, 2017 @05:36AM (#15139185)
Yet it took up all these years until clang for anyone to start taking static analysis seriously in C

In some circles maybe, but some industries have decades of experience applying static analysers to their C code, and companies have been selling static analysers throughout.

Re:The Development of the C Language by pjmlp on Thursday August 31, 2017 @05:51AM (#15139226)
Outside industries where MISRA-C is part of the daily vocabulary, I never seen any appreciation for C static analysers.
Re:The Development of the C Language by AnimalMuppet on Thursday August 31, 2017 @12:40PM (#15141545)
Some embedded systems places do this, even ones that are not safety-critical. It's more common as the level of concern rises. Medical instruments, for example, aren't MISRA, but at least some of them run static analyzers on C/C++ code. (All should...)