Remote Systems
v6.4.1

com.ibm.etools.systems.core.java
Interface IClassFileConstants

All Known Implementing Classes:
BasicClassFileParser

public interface IClassFileConstants


Field Summary
static int CONSTANT_CLASS
           
static int CONSTANT_DOUBLE
           
static int CONSTANT_FIELD_REF
           
static int CONSTANT_FLOAT
           
static int CONSTANT_INTEGER
           
static int CONSTANT_INTERFACE_METHOD_REF
           
static int CONSTANT_LONG
           
static int CONSTANT_METHOD_REF
           
static int CONSTANT_NAME_AND_TYPE
           
static int CONSTANT_STRING
           
static int CONSTANT_UTF8
           
 

Field Detail

CONSTANT_CLASS

public static final int CONSTANT_CLASS
See Also:
Constant Field Values

CONSTANT_FIELD_REF

public static final int CONSTANT_FIELD_REF
See Also:
Constant Field Values

CONSTANT_METHOD_REF

public static final int CONSTANT_METHOD_REF
See Also:
Constant Field Values

CONSTANT_INTERFACE_METHOD_REF

public static final int CONSTANT_INTERFACE_METHOD_REF
See Also:
Constant Field Values

CONSTANT_STRING

public static final int CONSTANT_STRING
See Also:
Constant Field Values

CONSTANT_INTEGER

public static final int CONSTANT_INTEGER
See Also:
Constant Field Values

CONSTANT_FLOAT

public static final int CONSTANT_FLOAT
See Also:
Constant Field Values

CONSTANT_LONG

public static final int CONSTANT_LONG
See Also:
Constant Field Values

CONSTANT_DOUBLE

public static final int CONSTANT_DOUBLE
See Also:
Constant Field Values

CONSTANT_NAME_AND_TYPE

public static final int CONSTANT_NAME_AND_TYPE
See Also:
Constant Field Values

CONSTANT_UTF8

public static final int CONSTANT_UTF8
See Also:
Constant Field Values

Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.