Bug#201348: O: lclint -- A tool for statically checking C programs.
Package: wnpp
Severity: normal
The current maintainer of lclint, Christian Meder
<meder@isr.uni-stuttgart.de>, has orphaned this package. Therefore, I
orphan this package now. If you want to be the new maintainer, please
take it -- see http://www.debian.org/devel/wnpp/index.html#howto-o for
detailed instructions how to adopt a package properly.
Some information about this package:
Package: lclint
Binary: lclint
Version: 1:2.4b-1.3
Priority: optional
Section: devel
Maintainer: Christian Meder <meder@isr.uni-stuttgart.de>
Build-Depends: debhelper (>> 3.0.0), bison, flex, csh
Architecture: any
Standards-Version: 3.1.1.1
Format: 1.0
Directory: pool/main/l/lclint
Files: 8f1ff55464943e751a55c4161fad500c 637 lclint_2.4b-1.3.dsc
ab9cbc54cbe8ac77e47d51c81632f858 1145469 lclint_2.4b.orig.tar.gz
dbfc49453bda54cbc78290488b83a0b7 170187 lclint_2.4b-1.3.diff.gz
Package: lclint
Priority: optional
Section: devel
Installed-Size: 2132
Maintainer: Christian Meder <meder@isr.uni-stuttgart.de>
Architecture: i386
Version: 1:2.4b-1.3
Depends: libc6 (>= 2.2.4-4)
Suggests: lclint-doc
Filename: pool/main/l/lclint/lclint_2.4b-1.3_i386.deb
Size: 613108
MD5sum: f6fc1e106ab7d768e16cc01744a1e1b4
Description: A tool for statically checking C programs.
LCLint is a tool for statically checking C programs. With minimal
effort, LCLint can be used as a better lint. If additional effort is
invested adding annotations to programs, LCLint can perform stronger
checks than can be done by any standard lint.
.
LCLint does many of the traditional lint checks including unused
declarations, type inconsistencies, use-before-definition, unreachable
code, ignored return values, execution paths with no return, likely
infinite loops, and fall-through cases. Our main focus, however, is on
more powerful checks that are made possible by additional information
given in source code annotations. Annotations are stylized comments
that document certain assumptions about functions, variables,
parameters, and types. They may be used to indicate where the
representation of a user-defined type is hidden, to limit where a global
variable may be used or modified, to constrain what a function
implementation may do to its parameters, and to express checked
assumptions about variables, types, structure fields, function
parameters, and function results. In addition to the checks
specifically enabled by annotations, many of the traditional lint checks
are improved by exploiting this additional information.
--
Martin Michlmayr
tbm@cyrius.com
Reply to: