Packages

  • package root
    Definition Classes
    root
  • package org
    Definition Classes
    root
  • 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 - org.opalj.bi) that can be used to create arbitrary representations.
    • a library to create a one-to-one in-memory representation of Java bytecode (Bytecode Disassembler - org.opalj.da).
    • a library to convert this representation to Java class files (Bytecode Creator - org.opalj.bc).
    • a library to create a representation of Java bytecode that facilitates writing simple static analyses (Bytecode Representation - org.opalj.br).
    • a library to create a stackless, three-address code representation of Java bytecode that facilitates writing complex static analyses (Three Address Code - org.opalj.tac).
    • a scalable, easily customizable framework for the abstract interpretation of Java bytecode (Abstract Interpretation Framework - org.opalj.ai).
    • a library to extract dependencies between code elements (Dependencies Extraction - org.opalj.de) and to facilitate checking architecture definitions (Architecture Validation - org.opalj.av).
    • a library for the lightweight manipulation and creation of Java bytecode (Bytecode Assembler - org.opalj.ba).
    • a library for parsing Android packages (APK - org.opalj.apk).
    • libraries for writing static analyses using the interprocedural finite distributive subset (IFDS - org.opalj.ifds) and interprocedural distributive environment (IDE - org.opal.ide) algorithms.

    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.

    Assertions

    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
    org
  • package br

    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.

    Definition Classes
    opalj
  • package fpcf
    Definition Classes
    br
  • package analyses
    Definition Classes
    fpcf
  • package immutability
  • package pointsto
  • CallStringContextProvider
  • ConfiguredPurity
  • ConfiguredPurityKey
  • ContextProvider
  • EagerL0AllocationFreenessAnalysis
  • EagerL0CompileTimeConstancyAnalysis
  • EagerL0PurityAnalysis
  • EagerSimpleFieldAccessInformationAnalysis
  • EagerStaticDataUsageAnalysis
  • L0AllocationFreenessAnalysis
  • L0AllocationFreenessAnalysisScheduler
  • L0CompileTimeConstancyAnalysis
  • L0CompileTimeConstancyAnalysisScheduler
  • L0PurityAnalysis
  • L0PurityAnalysisScheduler
  • L0SelfReferenceLeakageAnalysis
  • L1ThrownExceptionsAnalysis
  • LazyL0AllocationFreenessAnalysis
  • LazyL0CompileTimeConstancyAnalysis
  • LazyL0PurityAnalysis
  • LazyL1ThrownExceptionsAnalysis
  • LazyStaticDataUsageAnalysis
  • MethodComplexityAnalysis
  • SimpleContextProvider
  • SimpleFieldAccessInformationAnalysis
  • StaticDataUsageAnalysis
  • StaticDataUsageAnalysisScheduler
  • ThrownExceptionsAnalysisScheduler
  • package cli
    Definition Classes
    fpcf
  • package properties
    Definition Classes
    fpcf
p

org.opalj.br.fpcf

analyses

package analyses

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Package Members

  1. package immutability
  2. package pointsto

Type Members

  1. trait CallStringContextProvider extends ContextProvider
  2. class ConfiguredPurity extends AnyRef

  3. trait ContextProvider extends AnyRef

    Provides analyses with Contexts for method executions.

  4. class L0AllocationFreenessAnalysis extends FPCFAnalysis

    A simple analysis that identifies methods that never allocate any objects/arrays.

  5. trait L0AllocationFreenessAnalysisScheduler extends FPCFAnalysisScheduler
  6. class L0CompileTimeConstancyAnalysis extends FPCFAnalysis

    A simple analysis that identifies constant (effectively) final static fields that are deterministically initialized to the same value on every program execution.

    A simple analysis that identifies constant (effectively) final static fields that are deterministically initialized to the same value on every program execution. This analysis just examines the ConstantValue attribute of the field.

  7. trait L0CompileTimeConstancyAnalysisScheduler extends FPCFAnalysisScheduler
  8. class L0PurityAnalysis extends FPCFAnalysis

    Very simple, fast, sound but also imprecise analysis of the purity of methods.

    Very simple, fast, sound but also imprecise analysis of the purity of methods. See the org.opalj.br.fpcf.properties.Purity property for details regarding the precise semantics of (Im)Pure.

    This analysis is a very, very shallow implementation that immediately gives up, when something "complicated" (e.g., method calls which take objects) is encountered. It also does not perform any significant control-/data-flow analyses.

  9. trait L0PurityAnalysisScheduler extends FPCFAnalysisScheduler
  10. class L0SelfReferenceLeakageAnalysis extends FPCFAnalysis

    A shallow analysis that computes the self reference leakage property.

  11. class L1ThrownExceptionsAnalysis extends FPCFAnalysis

    Analysis of thrown exceptions; computes the org.opalj.br.fpcf.properties.ThrownExceptions property.

  12. class MethodComplexityAnalysis extends AnyRef

    A shallow analysis that tries to identify methods that are relatively simple, that is, which don't have loops and don't depend on other (more) complex methods.

    A shallow analysis that tries to identify methods that are relatively simple, that is, which don't have loops and don't depend on other (more) complex methods. For such methods it often makes sense to "inline them at analysis time".

  13. trait SimpleContextProvider extends ContextProvider
  14. class SimpleFieldAccessInformationAnalysis extends FPCFAnalysis

    A simple analysis that identifies every direct read and write access to a org.opalj.br.Field without using receiver or value information.

    A simple analysis that identifies every direct read and write access to a org.opalj.br.Field without using receiver or value information. If you need receiver or value information execute the similar analysis from TAC.

    Note

    Fields which are not accessed at all are not further considered.

    ,

    This analysis should never be executed together with its corresponding analysis from TAC to prevent overrides of receiver / value information.

  15. class StaticDataUsageAnalysis extends FPCFAnalysis

    A simple analysis that identifies methods that use global state that may vary during one or between several program executions.

  16. trait StaticDataUsageAnalysisScheduler extends FPCFAnalysisScheduler
  17. abstract class ThrownExceptionsAnalysisScheduler extends FPCFAnalysisScheduler

Ungrouped