• package root
    Definition Classes
  • package org
    Definition Classes
  • package opalj

    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:

    • a library (Common) which provides generally useful data-structures and algorithms for static analyses.
    • a framework for implementing lattice based static analyses (Static Analysis Infrastructure)
    • a framework for parsing Java bytecode (Bytecode Infrastructure) that can be used to create arbitrary representations.
    • a library to create a one-to-one in-memory representation of Java bytecode (Bytecode Disassembler).
    • a library to create a representation of Java bytecode that facilitates writing simple static analyses (Bytecode Representation -
    • a scalable, easily customizable framework for the abstract interpretation of Java bytecode (Abstract Interpretation Framework -
    • a library to extract dependencies between code elements and to facilitate checking architecture definitions.
    • a library for the lightweight manipulation and creation of Java bytecode (Bytecode Assembler).

    General Design Decisions

    Thread Safety

    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.)

    No null Values

    Unless 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.

    No Typecasts for Collections

    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.

    Definition Classes
  • package ai

    Implementation of an abstract interpretation (ai) framework – also referred to as OPAL.

    Implementation of an abstract interpretation (ai) framework – also referred to as OPAL.

    Please note that OPAL/the abstract interpreter just refers to the classes and traits defined in this package (ai). The classes and traits defined in the sub-packages (in particular in domain) are not considered to be part of the core of OPAL/the abstract interpreter.

    Definition Classes

    This framework assumes that the analyzed bytecode is valid; i.e., the JVM's bytecode verifier would be able to verify the code. Furthermore, load-time errors (e.g., LinkageErrors) are – by default – completely ignored to facilitate the analysis of parts of a project. In general, if the presented bytecode is not valid, the result is undefined (i.e., OPAL may report meaningless results, crash or run indefinitely).

    See also - Implements the abstract interpreter that processes a methods code and uses an analysis-specific domain to perform the abstract computations. - The core interface between the abstract interpretation framework and the abstract domain that is responsible for performing the abstract computations.

  • package fpcf
    Definition Classes
  • package analyses
    Definition Classes
  • package domain
    Definition Classes
  • L1DefaultDomainWithCFGAndDefUseAndSignatureRefinement
  • MethodCallsDomainWithMethodLockup
  • PrimitiveTACAIDomainWithSignatureRefinement
  • PropertyStoreBased
  • RefinedTypeLevelFieldAccessInstructions
  • RefinedTypeLevelInvokeInstructions
  • package properties
    Definition Classes

package domain

Type Members

  1. class L1DefaultDomainWithCFGAndDefUseAndSignatureRefinement[Source] extends DefaultDomainWithCFGAndDefUse[Source] with RefinedTypeLevelFieldAccessInstructions with RefinedTypeLevelInvokeInstructions
  2. trait MethodCallsDomainWithMethodLockup extends MethodCallsHandling

  3. class PrimitiveTACAIDomainWithSignatureRefinement extends TypeLevelDomain with ThrowAllPotentialExceptionsConfiguration with IgnoreSynchronization with DefaultTypeLevelHandlingOfMethodResults with TheMethod with RecordDefUse with RefinedTypeLevelFieldAccessInstructions with RefinedTypeLevelInvokeInstructions

    This is a primitive domain that can be used to transform Java bytecode to the three address representation offered by OPAL, which is build upon the result of a lightweight abstract interpretation.

  4. trait PropertyStoreBased extends TheProject

    Mixed in by (partial-)domains that query the property store to state the kinds of properties that are accessed.

  5. trait RefinedTypeLevelFieldAccessInstructions extends TypeLevelFieldAccessInstructions with PropertyStoreBased

    Queries the project information to identify fields with refined field type information.

  6. trait RefinedTypeLevelInvokeInstructions extends MethodCallsDomainWithMethodLockup with PropertyStoreBased