LPEX
3.6.7

com.ibm.lpex.core
Class LpexMatch

java.lang.Object
  extended by com.ibm.lpex.core.LpexMatch

public final class LpexMatch
extends Object

Matches parentheses, braces, square brackets, angle brackets.

In the current implementation all the text elements are used, not just the visible ones. SHOW elements are ignored.


Method Summary
static LpexDocumentLocation match(LpexView lpexView, LpexDocumentLocation loc)
          Match a parenthesis / brace / square bracket / angle bracket.
static LpexDocumentLocation match(LpexView lpexView, LpexDocumentLocation loc, boolean noisy)
          Match a parenthesis / brace / square bracket / angle bracket.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Method Detail

match

public static LpexDocumentLocation match(LpexView lpexView,
                                         LpexDocumentLocation loc)
Match a parenthesis / brace / square bracket / angle bracket. No error messages are issued. This method is intended primarily for use by other classes.

Parameters:
lpexView - document view
loc - document location of the character to match
Returns:
the matching document location, or
null if none for the parameters specified

match

public static LpexDocumentLocation match(LpexView lpexView,
                                         LpexDocumentLocation loc,
                                         boolean noisy)
Match a parenthesis / brace / square bracket / angle bracket. See also the match and findMatch default editor actions, and LpexCommonParser.matchToken(com.ibm.lpex.core.LpexDocumentLocation).

Parameters:
lpexView - document view
loc - document location of the character to match
noisy - true = issue a message for certain errors
Returns:
the matching document location, or
null if none for the parameters specified

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.