forked from secure-software-engineering/phasar
-
Notifications
You must be signed in to change notification settings - Fork 0
Coding Conventions
Bhuvan Sharma edited this page Jun 24, 2020
·
1 revision
Code unification of PhASAR, in order to meet one unique standard in the framework, is done according to the LLVM coding guidelines, wherever is possible. The LLVM coding guidelines can be found here:
https://llvm.org/docs/CodingStandards.html
In addition, the pre-commit script in githooks/
need to be copied into the ./git/hooks/
directory:
$ cp githooks/pre-commit .git/hooks/
The script runs some useful clang-tidy checks as well as clang-format over the entire code base just before your changes are committed in order to prevent the number of unnecessary merge conflicts and to unify the code base.
- Home
- Reference Material
- Getting Started:
- Building PhASAR
- Using PhASAR with Docker
- A few uses of PhASAR
- Writing a Data Flow Analysis
- Whole Program Analysis (Using WLLVM)
- Using PhASAR as a library (TBA)
- Coding Conventions
- Contributing to PhASAR
- Errors and bug reporting
- OS Support