OPAL is a Scala-based framework for the static analysis, manipulation and creation of Java bytecode.
OPAL is a Scala-based framework for the static analysis, manipulation and creation of Java bytecode. OPAL is designed with performance, scalability and adaptability in mind.
Its main components are:
Common) which provides generally useful data-structures and algorithms
for static analyses.Static Analysis Infrastructure)Bytecode Infrastructure - org.opalj.bi) that can be used to
create arbitrary representations.Bytecode Disassembler - org.opalj.da).Bytecode Creator - org.opalj.bc).Bytecode Representation - org.opalj.br).Three Address Code - org.opalj.tac).Abstract Interpretation Framework - org.opalj.ai).Dependencies Extraction - org.opalj.de) and to
facilitate checking architecture definitions (Architecture Validation - org.opalj.av).Bytecode Assembler - org.opalj.ba).APK - org.opalj.apk).IFDS - org.opalj.ifds) and interprocedural distributive environment (IDE - org.opal.ide) algorithms.Unless explicitly noted, OPAL is thread safe. I.e., the classes defined by OPAL can be considered to be thread safe unless otherwise stated. (For example, it is possible to read and process class files concurrently without explicit synchronization on the client side.)
null ValuesUnless explicitly noted, OPAL does not null values
I.e., fields that are accessible will never contain null values and methods will
never return null. If a method accepts null as a value for a parameter or
returns a null value it is always explicitly documented.
In general, the behavior of methods that are passed null values is undefined unless
explicitly documented.
For efficiency reasons, OPAL sometimes uses mutable data-structures internally.
After construction time, these data-structures are generally represented using
their generic interfaces (e.g., scala.collection.{Set,Map}). However, a downcast
(e.g., to add/remove elements) is always forbidden as it would effectively prevent
thread-safety.
OPAL makes heavy use of Scala's Assertion Facility to facilitate writing correct
code. Hence, for production builds (after thorough testing(!)) it is
highly recommend to build OPAL again using -Xdisable-assertions.
In this representation of Java bytecode references to a Java class file's constant pool and to attributes are replaced by direct references to the corresponding constant pool entries.
In this representation of Java bytecode references to a Java class file's constant pool and to attributes are replaced by direct references to the corresponding constant pool entries. This facilitates developing analyses and fosters comprehension.
Based on the fact that indirect references to constant pool entries are resolved and replaced by direct references this representation is called the resolved representation.
This representation of Java bytecode is considered as OPAL's standard representation for writing simple Scala based analyses. This representation is engineered such that it facilitates writing analyses that use pattern matching.
Container class, to represent a tamiflex log: https://github.com/secure-software-engineering/tamiflex
Stores TamiFlex log information for the current project