• 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. Furthermore, the concrete data-structure is always considered an implementation detail and may change at any time.


    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 ba

    Implementation of an eDSL for creating Java bytecode.

    Implementation of an eDSL for creating Java bytecode. The eDSL is designed to facilitate the creation of correct class files; i.e., whenever possible it tries to fill wholes. For example, when an interface is specified the library automatically ensures that the super class type is (initially) set to java.lang.Object as required by the JVM specification.

    This package in particular provides functionality to convert classes to org.opalj.da classes.

    Definition Classes
  • AccessModifier
  • AnnotatedInstructionElement
  • BRConstantsBuffer
  • CODE
  • CodeAttributeBuilder
  • CodeElement
  • ExceptionHandlerElement
  • ExceptionHandlerGenerator
  • FirstInstrumentation
  • InsertionPosition
  • InstructionElement
  • InstructionLikeElement
  • LabelElement
  • LabeledCode
  • LineNumberTableBuilder
  • PCMapping
  • ProjectBasedInMemoryClassLoader
  • PseudoInstruction
  • SecondInstrumentation
  • SimpleInstrumentationDemo
  • TRY
  • ThirdInstrumentation
  • ToDAConfig


final class AccessModifier extends AnyVal

Represents the access flags of a class (module), method or field declaration.

All standard access flags are predefined.

  1. To create a class file's, a field's or a method's access modifier, you can chain them using post fix notation, e.g.:


    or you just append the using '.', e.g.:

Linear Supertypes
AnyVal, Any
  1. Alphabetic
  2. By Inheritance
  1. AccessModifier
  2. AnyVal
  3. Any
  1. Hide All
  2. Show All
  1. Public
  2. All

Instance Constructors

  1. new AccessModifier(accessFlags: Int)

Value Members

  1. final def !=(arg0: Any): Boolean
    Definition Classes
  2. final def ##(): Int
    Definition Classes
  3. final def ==(arg0: Any): Boolean
    Definition Classes
  4. final def ABSTRACT: AccessModifier
  5. final def ANNOTATION: AccessModifier
  6. final def BRIDGE: AccessModifier
  7. final def ENUM: AccessModifier
  8. final def FINAL: AccessModifier
  9. final def INTERFACE: AccessModifier
  10. final def MANDATED: AccessModifier
  11. final def MODULE: AccessModifier
  12. final def NATIVE: AccessModifier
  13. final def OPEN: AccessModifier
  14. final def PRIVATE: AccessModifier
  15. final def PROTECTED: AccessModifier
  16. final def PUBLIC: AccessModifier
  17. final def STATIC: AccessModifier
  18. final def STATIC_PHASE: AccessModifier
  19. final def STRICT: AccessModifier
  20. final def SUPER: AccessModifier
  21. final def SYNCHRONIZED: AccessModifier
  22. final def SYNTHETIC: AccessModifier
  23. final def TRANSIENT: AccessModifier
  24. final def TRANSITIVE: AccessModifier
  25. final def VARARGS: AccessModifier
  26. final def VOLATILE: AccessModifier
  27. final def asInstanceOf[T0]: T0
    Definition Classes
  28. def getClass(): Class[_ <: AnyVal]
    Definition Classes
    AnyVal → Any
  29. final def isInstanceOf[T0]: Boolean
    Definition Classes
  30. def toString(): String
    Definition Classes

Inherited from AnyVal

Inherited from Any