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 purity

  Definition Classes

  analyses

•  class L1PurityAnalysis extends AbstractPurityAnalysis

  An inter-procedural analysis to determine a method's purity.

  An inter-procedural analysis to determine a method's purity.

  Definition Classes

  purity

  Note

  This analysis is sound only up to the usual standards, i.e. it does not cope with VirtualMachineErrors and may be unsound in the presence of native code, reflection or sun.misc.Unsafe. Calls to native methods are generally handled soundly as they are considered org.opalj.br.fpcf.properties.ImpureByAnalysis. There are no soundness guarantees in the presence of load-time transformation. Soundness in general depends on the soundness of the analyses that compute properties used by this analysis, e.g. field mutability.

  ,

  This analysis is sound even if the three address code hierarchy is not flat, it will produce better results for a flat hierarchy, though. This is because it will not assess the types of expressions other than org.opalj.tac.Vars.

  ,

  This analysis derives all purity levels except for the Externally variants. A configurable DomainSpecificRater is used to identify calls, expressions and exceptions that are LBDPure instead of LBImpure or any SideEffectFree purity level. Compared to the L0PurityAnalysis, it deals with all methods, even if their reference type parameters are mutable. It can handle accesses of (effectively) final instance fields, array loads, array length and virtual/interface calls. Array stores and field writes as well as (useless) synchronization on locally created, non-escaping objects/arrays are also handled. Newly allocated objects/arrays returned from callees are not identified.

• AnalysisState
• State

org.opalj.tac.fpcf.analyses.purity.L1PurityAnalysis

State