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) 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 - org.opalj.br).
    • 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 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.

    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 tac

    Common definitions related to the definition and processing of three address code.

    Common definitions related to the definition and processing of three address code.

    Definition Classes
    opalj
  • package fpcf
    Definition Classes
    tac
  • package analyses
    Definition Classes
    fpcf
  • package cg
    Definition Classes
    analyses
  • package escape
    Definition Classes
    analyses
  • package fieldassignability
    Definition Classes
    analyses
  • AbstractFieldAssignabilityAnalysis
  • EagerL0FieldAssignabilityAnalysis
  • EagerL1FieldAssignabilityAnalysis
  • EagerL2FieldAssignabilityAnalysis
  • L0FieldAssignabilityAnalysis
  • L0FieldAssignabilityAnalysisScheduler
  • L1FieldAssignabilityAnalysis
  • L1FieldAssignabilityAnalysisScheduler
  • L2FieldAssignabilityAnalysis
  • L2FieldAssignabilityAnalysisScheduler
  • LazyL0FieldAssignabilityAnalysis
  • LazyL1FieldAssignabilityAnalysis
  • LazyL2FieldAssignabilityAnalysis
  • package pointsto
    Definition Classes
    analyses
  • package purity
    Definition Classes
    analyses
p

org.opalj.tac.fpcf.analyses

fieldassignability

package fieldassignability

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Type Members

  1. trait AbstractFieldAssignabilityAnalysis extends FPCFAnalysis
  2. class L0FieldAssignabilityAnalysis extends FPCFAnalysis

    Determines if a private, static, non-final field is always initialized at most once or if a field is or can be mutated after (lazy) initialization.

    Determines if a private, static, non-final field is always initialized at most once or if a field is or can be mutated after (lazy) initialization. Field read and writes at initialization time (e.g., if the current class object is registered in some publicly available data-store) are not considered. This is in-line with the semantics of final, which also does not prevent reads of partially initialized objects.

  3. trait L0FieldAssignabilityAnalysisScheduler extends FPCFAnalysisScheduler
  4. class L1FieldAssignabilityAnalysis extends AbstractFieldAssignabilityAnalysis

    Simple analysis that checks if a private (static or instance) field is always initialized at most once or if a field is or can be mutated after (lazy) initialization.

    Simple analysis that checks if a private (static or instance) field is always initialized at most once or if a field is or can be mutated after (lazy) initialization.

    Note

    Requires that the 3-address code's expressions are not deeply nested.

  5. sealed trait L1FieldAssignabilityAnalysisScheduler extends FPCFAnalysisScheduler
  6. class L2FieldAssignabilityAnalysis extends AbstractFieldAssignabilityAnalysis with FPCFAnalysis

    Determines the assignability of a field.

    Determines the assignability of a field.

    Note

    Requires that the 3-address code's expressions are not deeply nested.

  7. trait L2FieldAssignabilityAnalysisScheduler extends FPCFAnalysisScheduler

Value Members

  1. object EagerL0FieldAssignabilityAnalysis extends L0FieldAssignabilityAnalysisScheduler with BasicFPCFEagerAnalysisScheduler

    Factory object to create instances of the FieldImmutabilityAnalysis.

  2. object EagerL1FieldAssignabilityAnalysis extends L1FieldAssignabilityAnalysisScheduler with BasicFPCFEagerAnalysisScheduler

    Executor for the eager field assignability analysis.

  3. object EagerL2FieldAssignabilityAnalysis extends L2FieldAssignabilityAnalysisScheduler with BasicFPCFEagerAnalysisScheduler

    Executor for the eager field assignability analysis.

  4. object LazyL0FieldAssignabilityAnalysis extends L0FieldAssignabilityAnalysisScheduler with BasicFPCFLazyAnalysisScheduler
  5. object LazyL1FieldAssignabilityAnalysis extends L1FieldAssignabilityAnalysisScheduler with BasicFPCFLazyAnalysisScheduler

    Executor for the lazy field assignability analysis.

  6. object LazyL2FieldAssignabilityAnalysis extends L2FieldAssignabilityAnalysisScheduler with BasicFPCFLazyAnalysisScheduler

    Executor for the lazy field assignability analysis.

Ungrouped