LPEX
3.6.6

com.ibm.lpex.core
Interface LpexParser

All Known Implementing Classes:
Cobol400Parser, Cobol400SqlCicsParser, CobolParser, CobolSqlCicsParser, CppCicsParser, CppCicsParserAIX, CppCicsParserOS2, CppCicsParserWIN, CppParser, CppParserAIX, CppParserOS2, CppParserWIN, CppSqlParser, CppSqlParserAIX, CppSqlParserOS2, CppSqlParserWIN, FortranFixedFormParser, FortranParser, HtmlParser, ILECobolParser, ILECobolSqlCicsParser, JavaParser, JavaSqlParser, JclParser, JclParserJES2ESA, LpexCommonParser, PliParser, PropertiesParser, RexxParser, SqlParser, TestParser1, TestParser2, XmlParser, XslParser

public interface LpexParser

Interface LpexParser can be implemented to define a document parser.

A parser is associated with one particular view of a document. The parser must have a constructor whose parameter is this view:

   MyLpexParser(LpexView lpexView) {} 

See Also:
LpexCommonParser

Method Summary
 String getProperty(String key)
          Retrieve a parser property.
 void parse(int element)
          Incremental parse.
 void resetParser()
          Remove all of the parser specifics from the document view.
 void totalParse()
          Total parse.
 

Method Detail

resetParser

void resetParser()
Remove all of the parser specifics from the document view. For example, remove any listeners you added, and dispose of any resources. Note that classes, style attributes, commands, and actions are already automatically removed by the editor.


totalParse

void totalParse()
Total parse. Parse the entire document.


parse

void parse(int element)
Incremental parse. Parse change(s) to a document.

Parameters:
element - an element affected by a committed change in this view

getProperty

String getProperty(String key)
Retrieve a parser property.

Parameters:
key - property name

LPEX
3.6.6

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.