Are you tired of null pointer exceptions, unintended side effects, SQL injections, concurrency errors, mistaken equality tests, and other run-time errors that appear during testing or in the field?
The Checker Framework enhances Java’s type system to make it more powerful and useful. This lets software developers detect and prevent errors in their Java programs. The Checker Framework includes compiler plug-ins ("checkers") that find bugs or verify their absence. It also permits you to write your own compiler plug-ins.
Quick start: go directly to the Installation instructions and tutorial.
@NonNulltype qualifier, use the Julia Analyzer, Nit, or JastAdd
@ReadOnlytype qualifier, use Javarifier
.classfiles. It also provides a representation (called an “annotation file”) for annotations that is outside the source code or the
.classfile. The tools support both Java 5 declaration annotations and Java 8 type annotations.
If you have a question, then first see whether your question is answered in one of the manuals listed under Documentation below. If none of those documents answers your question, then use one of the mailing lists.
We welcome questions, suggestions, patches, reports about case studies, and other contributions. Please let us know how we can improve the Checker Framework!
You can also use the mailing lists to give help. Here are just a few examples:
Another way to help is to tell your friends and colleagues about the usefulness and practicality of type annotations, or to report your successes to the mailing lists.
If you encounter a problem, please submit a bug report so that we can fix it. To submit a bug report, read these instructions, and then use the Checker Framework issue tracker.
Last updated: 1 Feb 2016