LPEX
3.6.7

com.ibm.lpex.cobol
Class CobolParser.TokenFragment

java.lang.Object
  extended by com.ibm.lpex.cobol.CobolParser.TokenFragment
Enclosing class:
CobolParser

public class CobolParser.TokenFragment
extends Object

A TokenFragment contains information about part of a token. If a token extends over multiple lines (for example, in the case of continuation lines), then several TokenFragment objects will be needed to describe the entire token.


Field Summary
 int _element
          The element for this token fragment.
 int _endBytePosition
          The end byte position of this token fragment.
 int _endCharacterPosition
          The end character position of this token fragment.
 CobolParser.TokenFragment _next
          The next token fragment.
 int _startBytePosition
          The start byte position of this token fragment.
 int _startCharacterPosition
          The start character position of this token fragment.
 
Constructor Summary
CobolParser.TokenFragment()
          Construct a new token fragment.
 
Method Summary
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

_element

public int _element
The element for this token fragment.


_startCharacterPosition

public int _startCharacterPosition
The start character position of this token fragment.


_startBytePosition

public int _startBytePosition
The start byte position of this token fragment.


_endCharacterPosition

public int _endCharacterPosition
The end character position of this token fragment.


_endBytePosition

public int _endBytePosition
The end byte position of this token fragment.


_next

public CobolParser.TokenFragment _next
The next token fragment.

Constructor Detail

CobolParser.TokenFragment

public CobolParser.TokenFragment()
Construct a new token fragment. If not the first, link it in.


LPEX
3.6.7

Copyright © 2012 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.