Home » openjdk-7 » net.bonzoun » cocodonkey » [javadoc | source]
public class: TokenMgrError [javadoc | source]

All Implemented Interfaces:

Field Summary
static final  int LEXICAL_ERROR    Lexical error occured. 
static final  int STATIC_LEXER_ERROR    An attempt wass made to create a second instance of a static token manager. 
static final  int INVALID_LEXICAL_STATE    Tried to change to an invalid lexical state. 
static final  int LOOP_DETECTED    Detected (and bailed out of) an infinite loop in the token manager. 
 int errorCode    Indicates the reason why the exception is thrown. It will have one of the above 4 values. 
Fields inherited from java.lang.Error:
 public TokenMgrError() 
 public TokenMgrError(String message,
    int reason) 
 public TokenMgrError(boolean EOFSeen,
    int lexState,
    int errorLine,
    int errorColumn,
    String errorAfter,
    char curChar,
    int reason) 
Method from net.bonzoun.cocodonkey.TokenMgrError Summary:
addEscapes,   getMessage
Methods from java.lang.Throwable:
addSuppressed,   fillInStackTrace,   getCause,   getLocalizedMessage,   getMessage,   getStackTrace,   getStackTraceDepth,   getStackTraceElement,   getSuppressed,   initCause,   printStackTrace,   printStackTrace,   printStackTrace,   setStackTrace,   toString
Methods from java.lang.Object:
clone,   equals,   finalize,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from net.bonzoun.cocodonkey.TokenMgrError Detail:
 protected static final String addEscapes(String str) 
    Replaces unprintable characters by their espaced (or unicode escaped) equivalents in the given string
 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.