Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.parsers
Interface IISeriesEditorSyntaxChecker

All Known Implementing Classes:
ISeriesEditorCLSyntaxChecker, ISeriesEditorCobolSyntaxChecker, ISeriesEditorDDSSyntaxChecker, ISeriesEditorRPGILESyntaxChecker, ISeriesEditorRPGOPMSyntaxChecker

public interface IISeriesEditorSyntaxChecker

Implemented by syntax checkers.


Field Summary
static String Copyright
           
 
Method Summary
 ISeriesEditorSyntaxError[] checkSyntax(int iLineStart, int iLineEnd)
          Syntax checks the given line range.
 void checkSyntaxOfCurrentLine()
          Syntax checks the line of the document that the cursor is on.
 void checkSyntaxOfDocument()
          Syntax checks all the lines of the document.
 void checkSyntaxOfRange(int iLineStart, int iLineEnd)
          Syntax checks all the lines of the document.
 void checkSyntaxOfSelection()
          Syntax checks all the lines of the selected range.
 boolean isAvailable()
          Returns whether the syntax checker is available.
 

Field Detail

Copyright

static final String Copyright
See Also:
Constant Field Values
Method Detail

checkSyntax

ISeriesEditorSyntaxError[] checkSyntax(int iLineStart,
                                       int iLineEnd)
Syntax checks the given line range.


checkSyntaxOfCurrentLine

void checkSyntaxOfCurrentLine()
Syntax checks the line of the document that the cursor is on.


checkSyntaxOfDocument

void checkSyntaxOfDocument()
Syntax checks all the lines of the document.


checkSyntaxOfSelection

void checkSyntaxOfSelection()
Syntax checks all the lines of the selected range.


checkSyntaxOfRange

void checkSyntaxOfRange(int iLineStart,
                        int iLineEnd)
Syntax checks all the lines of the document.


isAvailable

boolean isAvailable()
Returns whether the syntax checker is available.


Rational Developer for Power Systems Software
V7.6

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