Glossary · Automation software engineering and architecture
Linting
Also known as: Lint, Linter
German: Linting
In software engineering, linting is the automated checking of source code, configuration or documentation files for stylistic issues, suspicious constructs and violations of coding rules, using a tool called a linter, usually without executing the code.
- Software engineering
In one sentence
Linting automatically checks source code or other files for style issues, suspicious constructs and rule violations without running them.
Example
The pipeline runs a linter on the structured text code that flags unused variables, implicit type conversions and missing comments in function block headers.
How it applies
- Engineering: Linters give fast feedback in the editor and in the Build pipeline. They enforce the automatable part of a Coding guideline, leaving reviewers free to focus on logic and design.
- Automation context: Linting and static analysis tools exist for IEC 61131-3 code, often from engineering tool vendors or third parties, as well as for C/C++, Python, configuration files and HMI projects.
- Documentation: Linters also work on documentation sources: prose linters check terminology and style rules, and markup validators check DITA, Markdown or XML structure. The documentation team can use the same pipeline as developers for these checks.
Linting vs. static code analysis
The line is blurred. Linting usually refers to lighter checks of style and simple defects; Static code analysis also includes deeper analyses such as data flow, value ranges and potential runtime errors. Both examine code without executing it.