org.jomc.util
Class TokenMgrError

Package class diagram package TokenMgrError
java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Error
          extended by org.jomc.util.TokenMgrError
All Implemented Interfaces:
Serializable

public class TokenMgrError
extends Error

Token Manager Error.

See Also:
Serialized Form

Constructor Summary
TokenMgrError()
          No arg constructor.
TokenMgrError(boolean EOFSeen, int lexState, int errorLine, int errorColumn, String errorAfter, char curChar, int reason)
          Full Constructor.
TokenMgrError(String message, int reason)
          Constructor with message and reason.
 
Method Summary
protected static String addEscapes(String str)
          Replaces unprintable characters by their escaped (or unicode escaped) equivalents in the given string
 String getMessage()
          You can also modify the body of this method to customize your error messages.
protected static String LexicalError(boolean EOFSeen, int lexState, int errorLine, int errorColumn, String errorAfter, char curChar)
          Returns a detailed message for the Error when it is thrown by the token manager to indicate a lexical error.
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Constructor Detail

TokenMgrError

public TokenMgrError()
No arg constructor.


TokenMgrError

public TokenMgrError(String message,
                     int reason)
Constructor with message and reason.


TokenMgrError

public TokenMgrError(boolean EOFSeen,
                     int lexState,
                     int errorLine,
                     int errorColumn,
                     String errorAfter,
                     char curChar,
                     int reason)
Full Constructor.

Method Detail

addEscapes

protected static final String addEscapes(String str)
Replaces unprintable characters by their escaped (or unicode escaped) equivalents in the given string


LexicalError

protected static String LexicalError(boolean EOFSeen,
                                     int lexState,
                                     int errorLine,
                                     int errorColumn,
                                     String errorAfter,
                                     char curChar)
Returns a detailed message for the Error when it is thrown by the token manager to indicate a lexical error. Parameters : EOFSeen : indicates if EOF caused the lexical error curLexState : lexical state in which this error occurred errorLine : line number when the error occurred errorColumn : column number when the error occurred errorAfter : prefix that was seen before this error occurred curchar : the offending character Note: You can customize the lexical error message by modifying this method.


getMessage

public String getMessage()
You can also modify the body of this method to customize your error messages. For example, cases like LOOP_DETECTED and INVALID_LEXICAL_STATE are not of end-users concern, so you can return something like : "Internal Error : Please file a bug report .... " from this method for such cases in the release version of your parser.

Overrides:
getMessage in class Throwable


Copyright © 2005-2012 The JOMC Project. All Rights Reserved.Get JOMC at SourceForge.net. Fast, secure and Free Open Source software downloads
Please note that this documentation is maintained by non-native english speaking authors. As such, you may encounter phrases or wordings which seem imprecise or may even have a totally different meaning to native english speaking readers than what the individual author was trying to express. If you are a native english speaking reader and find any such phrases or wordings we kindly ask you to send an email to the corresponding author and help us improve this documentation in order to avoid misunderstandings. You will find the authors' email addresses at the top of each class. Please accept our apologies for any inconvenience caused.