4:59
| Original author(s) | Stephen C. Johnson |
|---|---|
| Developer(s) | AT&T Bell Laboratories |
| Initial release | July 26, 1978[1] |
| Written in | C |
| Operating system | Cross-platform |
| Available in | English |
| Type | Static program analysis tools |
| License | Originally proprietary commercial software, now free software under a BSD-like license[2][3] |
lint, or a linter, is a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs.[4] The term originates from a Unix utility that examined C language source code.[1]
Stephen C. Johnson, a computer scientist at Bell Labs, came up with lint in 1978 while debugging the yacc grammar he was writing for C and dealing with portability issues stemming from porting Unix to a 32-bit machine.[5][1] The term "lint" was derived from the name of the tiny bits of fiber and fluff shed by clothing, as the command should act like a dryer machine lint trap, detecting small errors with big effects. In 1979, lint was used outside of Bell Labs for the first time in the seventh version (V7) of the Unix operating system.
Over the years, different versions of lint were developed for many C and C++ compilers and while modern-day compilers have lint-like functions, lint-like tools have also advanced their capabilities. For example, Gimpel's PC-Lint, used to analyze C++ source code, is still being sold even though it was introduced in 1985.[5]
The analysis performed by lint-like tools can also be performed by an optimizing compiler, which aims to generate faster code. In his original 1978 paper, Johnson addressed this issue, concluding that "the general notion of having two programs is a good one" because they concentrated on different things, thereby allowing the programmer to "concentrate at one stage of the programming process solely on the algorithms, data structures, and correctness of the program, and then later retrofit, with the aid of lint, the desirable properties of universality and portability".[1]
Even though modern compilers have evolved to include many of lint's historical functions, lint-like tools have also evolved to detect an even wider variety of suspicious constructs. These include "warnings about syntax errors, uses of undeclared variables, calls to deprecated functions, spacing and formatting conventions, misuse of scope, implicit fallthrough in switch statements, missing license headers, [and]...dangerous language features".[6]
Lint-like tools are especially useful for dynamically typed languages like JavaScript and Python. Because the compilers of such languages typically do not enforce as many and as strict rules prior to execution, linter tools can also be used as simple debuggers for finding common errors (e.g. syntactic discrepancies) as well as hard-to-find errors such as heisenbugs (drawing attention to suspicious code as "possible errors").[7] Lint-like tools generally perform static analysis of source code.[8]
Lint-like tools have also been developed for other aspects of language, including grammar and style guides.[citation needed]
Fortran compilers using space-squeezing techniques (e.g. IBM 1130)[9] made it impossible for the compiler to see the problem with lines like:
|journal= (help)
similar to DEC's Source Code Analyzer, .. comes into play much earlier .. before users compile their programs
Fortran90-lint, for Fortran 90 program analysis, also other tools, from http://www.cleanscape.net/stdprod/ftp/ftpflint.html
There is a public domain version of lint for FORTRAN 77 called ftnchek
By: Wikipedia.org
Edited: 2021-06-18 15:16:39
Source: Wikipedia.org