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 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 fieldaccess
    Definition Classes
    analyses
  • package reflection
    Definition Classes
    fieldaccess
  • ActualParameterBasedFieldMatcher
  • ActualReceiverBasedFieldMatcher
  • AllFieldsMatcher
  • ClassBasedFieldMatcher
  • FieldGetAnalysis
  • FieldInstanceBasedReflectiveFieldAccessAnalysis
  • FieldMatcher
  • FieldMatching
  • FieldSetAnalysis
  • LBTypeBasedFieldMatcher
  • MatcherUtil
  • MethodHandleInvokeAnalysis
  • MethodHandlesUtil
  • NameBasedFieldMatcher
  • NoFieldsMatcher
  • NonStaticFieldMatcher
  • PropertyBasedFieldMatcher
  • PublicFieldMatcher
  • ReflectionAnalysis
  • ReflectionRelatedFieldAccessesAnalysis
  • ReflectionRelatedFieldAccessesAnalysisScheduler
  • StaticFieldMatcher
  • UBTypeBasedFieldMatcher

package reflection

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Type Members

  1. class ActualParameterBasedFieldMatcher extends FieldMatcher

    Considers all fields to which the given parameter would be assignable.

  2. class ActualReceiverBasedFieldMatcher extends FieldMatcher

    Considers all fields that either - are static fields AND the receiver may be null or - are instance fields AND the receiver may not be null AND the receiver is a value at least a subtype of the class declaring the field

  3. class ClassBasedFieldMatcher extends FieldMatcher
  4. class FieldGetAnalysis extends ReflectionAnalysis with FieldInstanceBasedReflectiveFieldAccessAnalysis
  5. sealed trait FieldInstanceBasedReflectiveFieldAccessAnalysis extends ReflectionAnalysis with TypeConsumerAnalysis
  6. trait FieldMatcher extends AnyRef

    Used to determine whether a certain field should be considered as a target for a reflective access.

    Used to determine whether a certain field should be considered as a target for a reflective access. These accesses should be resolved by chaining matchers in FieldMatching.getPossibleFields.

  7. class FieldSetAnalysis extends ReflectionAnalysis with FieldInstanceBasedReflectiveFieldAccessAnalysis
  8. class LBTypeBasedFieldMatcher extends FieldMatcher

    Considers all fields that have a type to which the given type is assignable.

    Considers all fields that have a type to which the given type is assignable. The given type thus acts as the lower bound type. Usually encountered in parameters of field accesses.

  9. class MethodHandleInvokeAnalysis extends ReflectionAnalysis with TypeConsumerAnalysis
  10. final class NameBasedFieldMatcher extends FieldMatcher
  11. sealed trait PropertyBasedFieldMatcher extends FieldMatcher
  12. sealed trait ReflectionAnalysis extends TACAIBasedAPIBasedAnalysis
  13. class ReflectionRelatedFieldAccessesAnalysis extends FPCFAnalysis

    Records field accesses made through various reflective tools.

  14. class UBTypeBasedFieldMatcher extends FieldMatcher

    Considers all fields that have a type that is assignable to the given type.

    Considers all fields that have a type that is assignable to the given type. The given type thus acts as the upper bound type. Usually encountered in return / cast types of field accesses.

Value Members

  1. object AllFieldsMatcher extends FieldMatcher
  2. object FieldMatching
  3. object MatcherUtil
  4. object MethodHandlesUtil
  5. object NoFieldsMatcher extends FieldMatcher
  6. object NonStaticFieldMatcher extends PropertyBasedFieldMatcher
  7. object PublicFieldMatcher extends PropertyBasedFieldMatcher
  8. object ReflectionRelatedFieldAccessesAnalysis
  9. object ReflectionRelatedFieldAccessesAnalysisScheduler extends BasicFPCFEagerAnalysisScheduler
  10. object StaticFieldMatcher extends PropertyBasedFieldMatcher

Ungrouped