LPEX
4.4.0

com.ibm.lpex.sql
Class SqlLexerClasses

java.lang.Object
  extended by com.ibm.lpex.sql.SqlLexerClasses

public final class SqlLexerClasses
extends Object

Element classes for the SQL lexer. The classes used by the SQL lexer must be first defined and registered by the host document parser. Using certain classes in both the host and the SQL parser allows common features and tools to view the document as one integrated unit. In incremental parsing, for example, the host parser will interpret the SQL forward & backward link classes when evaluating the optimal parse range. Also, the Errors filtered view will show the errors in the entire document.


Constructor Summary
SqlLexerClasses(LpexView lpexView)
          Default set of SQL lexer classes.
SqlLexerClasses(LpexView lpexView, long code, long forwardLink, long backwardLink, long comment, long error, long sqlStatement)
          Construct a set of SQL lexer classes.
 
Method Summary
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

SqlLexerClasses

public SqlLexerClasses(LpexView lpexView)
Default set of SQL lexer classes.

Parameters:
lpexView - the LPEX document view associated with the lexer

SqlLexerClasses

public SqlLexerClasses(LpexView lpexView,
                       long code,
                       long forwardLink,
                       long backwardLink,
                       long comment,
                       long error,
                       long sqlStatement)
Construct a set of SQL lexer classes.

Parameters:
lpexView - the LPEX document view associated with the lexer

LPEX
4.4.0

Copyright � 2016 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.