LPEX
4.6.0

API Documentation

Packages 
Package Description
com.ibm.lpex.alef
This package provides advanced line-oriented editing functions for Eclipse technology plug-ins.
com.ibm.lpex.alef.contentassist
This package provides code-assist support.
com.ibm.lpex.alef.internal  
com.ibm.lpex.alef.preferences
This package provides Eclipse platform preference pages for the LPEX editors.
com.ibm.lpex.bidi  
com.ibm.lpex.cc
This package provides lexical analyzer code and common support for several document parsers.
com.ibm.lpex.cics
This package provides CICS (Customer Information Control System) support for document parsers.
com.ibm.lpex.cobol
This package provides COBOL (Common Business Oriented Language) document parsers.
com.ibm.lpex.core
This package provides the base implementation of the LPEX editor widget.
com.ibm.lpex.cpp
This package provides C/C++ document parsers.
com.ibm.lpex.fortran
This package provides Fortran document parsers.
com.ibm.lpex.html
This package provides an HTML (Hypertext Markup Language) document parser.
com.ibm.lpex.java
This package provides Java language document parsers.
com.ibm.lpex.jcl
This package provides JCL (Job Control Language) document parsers.
com.ibm.lpex.pli
This package provides a PL/I document parser.
com.ibm.lpex.prop
This package provides a document parser for Java properties files.
com.ibm.lpex.rexx
This package provides a REXX document parser.
com.ibm.lpex.samples
This package contains samples for those who wish to extend the editor.
com.ibm.lpex.sql
This package provides SQL (Structured Query Language) support for document parsers.
com.ibm.lpex.xml
This package provides an XML (eXtensible Markup Language) document parser.
com.ibm.lpex.xsl
This package provides an XSL (eXtensible Stylesheet Language) document parser.
LPEX
4.6.0

Copyright ? 2020 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.