Version 28 of Static syntax analysis

Updated 2004-04-02 09:06:44

This is a sub-category of Category Debugging.

Static syntax analysis is the process of looking at a text file and attempting to identify errors, warnings, etc. from the text without executing the code. This is tricky to do in-depth because in an interpretive environment, programmers often make use of dynamic techniques for code generation, etc. These dynamic code fragments typically won't be evaluated during a static syntax sweep. Another short-coming, at least as far as procheck and frink go, is that they operate only on the source code specified on the command line. This means that calls to autoloaded or sourceed commands are treated as unknowns, unless the file in which they are defined was specified before the invocation.

A C programmer will be familar with a program called lint; this program provides static syntax analysis for C.


Any tool doing SSA and having its own page should have a link to this page on its page, like for normal categories. That way clicking on the title of this page will then deliver a list of tools in this sub-category.

The list of options below is only for external references we cannot categorize directly, and unnamed tools which are part of greater system. The moment such tools get their own page here they will be removed from the list below and can be reached through the title of this page.

  • Frink has some syntax checking and style suggestion for static analysis.
  • XotclIDE have syntax checker for Tcl and XOTcl code.
  • TDK has a program called tclchecker that does static syntax checking.
  • Nagelfar is an extensible syntax checker.
  • See a page by Cameron Laird for more [L1 ].

[ Give examples of use. ]

See also


[ Category Debugging ]