antic(1)

NAME
antic - Anti-C control flow analysis

SYNOPSIS
  antic [options] <file|dir ...>

DESCRIPTION
AntiC performs control flow analysis to detect situations, where control can be passed from one case branch to another e.g. if programmer forget about BREAK statement.

Input of AntiC should be valid C/C++ or Java program with no syntax errors. If there are some syntax errors in the program, AntiC can detect some of them and produce error message, but it doesn't try to perform full syntax checking and can't recover after some errors.

Almost all C statements can contain as its sub-part either single statement or block of statements (enclosed by braces). Unnoticed semicolon or wrong alignment can confuse programmer about real statement's body. And compiler can't produce any warnings, because it deals with stream of tokens, without information about code alignment.

An example:

    if (x > y);
    {
        int tmp = x;
        x = y;
        y = tmp;
    }

Full manual is at /usr/share/doc/jlint/manual.html

OPTIONS

-java
    Select Java instead of default C language.

-relax-else
    Do less strict else-statement testing.

-tab SIZE
    Set display putput option.

-version
    Display version.

ENVIRONMENT
None.

FILES
None.

SEE ALSO
jlint(1)

AUTHORS
This manual page was written by Jari Aalto <jari.aalto@cante.net>. Released under license GNU GPL version 2 or (at your option) any later version. For more information about the license, visit <http://www.gnu.org/copyleft/gpl.html>.