Examples of RecognitionException

antlr.RecognitionException
org.antlr.runtime.RecognitionException
The root of the ANTLR exception hierarchy. To avoid English-only error messages and to generally make things as flexible as possible, these exceptions are not created with strings, but rather the information necessary to generate an error. Then the various reporting methods in Parser and Lexer can be overridden to generate a localized error message. For example, MismatchedToken exceptions are built with the expected token type. So, don't expect getMessage() to return anything. Note that as of Java 1.4, you can access the stack trace, which means that you can compute the complete trace of rules from the start symbol. This gives you considerable context information with which to generate useful error messages. ANTLR generates code that throws exceptions upon recognition error and also generates code to catch these exceptions in each rule. If you want to quit upon first error, you can turn off the automatic error handling mechanism using rulecatch action, but you still need to override methods mismatch and recoverFromMismatchSet. In general, the recognition exceptions can track where in a grammar a problem occurred and/or what was the expected input. While the parser knows its state (such as current input symbol and line info) that state can change before the exception is reported so current token index is computed and stored at exception time. From this info, you can perhaps print an entire line of input not just a single token, for example. Better to just say the recognizer had a problem and then let the parser figure out a fancy report.
org.antlr.runtime3_3_0.RecognitionException
The root of the ANTLR exception hierarchy. To avoid English-only error messages and to generally make things as flexible as possible, these exceptions are not created with strings, but rather the information necessary to generate an error. Then the various reporting methods in Parser and Lexer can be overridden to generate a localized error message. For example, MismatchedToken exceptions are built with the expected token type. So, don't expect getMessage() to return anything. Note that as of Java 1.4, you can access the stack trace, which means that you can compute the complete trace of rules from the start symbol. This gives you considerable context information with which to generate useful error messages. ANTLR generates code that throws exceptions upon recognition error and also generates code to catch these exceptions in each rule. If you want to quit upon first error, you can turn off the automatic error handling mechanism using rulecatch action, but you still need to override methods mismatch and recoverFromMismatchSet. In general, the recognition exceptions can track where in a grammar a problem occurred and/or what was the expected input. While the parser knows its state (such as current input symbol and line info) that state can change before the exception is reported so current token index is computed and stored at exception time. From this info, you can perhaps print an entire line of input not just a single token, for example. Better to just say the recognizer had a problem and then let the parser figure out a fancy report.
org.antlr.v4.runtime.RecognitionException
The root of the ANTLR exception hierarchy. In general, ANTLR tracks just 3 kinds of errors: prediction errors, failed predicate errors, and mismatched input errors. In each case, the parser knows where it is in the input, where it is in the ATN, the rule invocation stack, and what kind of problem occurred.
org.eclipse.persistence.internal.libraries.antlr.runtime.RecognitionException
The root of the ANTLR exception hierarchy. To avoid English-only error messages and to generally make things as flexible as possible, these exceptions are not created with strings, but rather the information necessary to generate an error. Then the various reporting methods in Parser and Lexer can be overridden to generate a localized error message. For example, MismatchedToken exceptions are built with the expected token type. So, don't expect getMessage() to return anything. Note that as of Java 1.4, you can access the stack trace, which means that you can compute the complete trace of rules from the start symbol. This gives you considerable context information with which to generate useful error messages. ANTLR generates code that throws exceptions upon recognition error and also generates code to catch these exceptions in each rule. If you want to quit upon first error, you can turn off the automatic error handling mechanism using rulecatch action, but you still need to override methods mismatch and recoverFromMismatchSet. In general, the recognition exceptions can track where in a grammar a problem occurred and/or what was the expected input. While the parser knows its state (such as current input symbol and line info) that state can change before the exception is reported so current token index is computed and stored at exception time. From this info, you can perhaps print an entire line of input not just a single token, for example. Better to just say the recognizer had a problem and then let the parser figure out a fancy report.
org.jostraca.comp.antlr.RecognitionException

Examples of org.antlr.runtime.RecognitionException


        assertEquals("unexpected errors: "+equeue, 1, equeue.errors.size());


        int expectedMsgID = ErrorManager.MSG_WILDCARD_AS_ROOT;
        Object expectedArg = null;
        RecognitionException expectedExc = null;
        GrammarSyntaxMessage expectedMessage =
            new GrammarSyntaxMessage(expectedMsgID, g, null, expectedArg, expectedExc);


        checkError(equeue, expectedMessage);        
    }

View Full Code Here

Examples of org.antlr.runtime3_3_0.RecognitionException

      String lineS = elements[3];
      String posS = elements[4];
      Class excClass = null;
      try {
        excClass = Class.forName(excName);
        RecognitionException e =
          (RecognitionException)excClass.newInstance();
        e.index = Integer.parseInt(indexS);
        e.line = Integer.parseInt(lineS);
        e.charPositionInLine = Integer.parseInt(posS);
        listener.recognitionException(e);

View Full Code Here

Examples of org.antlr.v4.runtime.RecognitionException

    public ANTLRErrorStrategy createErrorStrategy() {
        return new BailErrorStrategy() {
            private void bail(Parser recognizer, Exception exc, String additionalHint)
                        throws ParseCancellationException
            {
                RecognitionException re = (RecognitionException)exc.getCause();
                int offendingState = re.getOffendingState();
                Token offendingToken = re.getOffendingToken();
                int offendingTokenType = offendingToken.getType();


                String msg = getErrorMessage(offendingState, offendingTokenType);


                StringBuilder sb = new StringBuilder();

View Full Code Here

Examples of org.eclipse.persistence.internal.libraries.antlr.runtime.RecognitionException

      String lineS = elements[3];
      String posS = elements[4];
      Class excClass = null;
      try {
        excClass = Class.forName(excName);
        RecognitionException e =
          (RecognitionException)excClass.newInstance();
        e.index = Integer.parseInt(indexS);
        e.line = Integer.parseInt(lineS);
        e.charPositionInLine = Integer.parseInt(posS);
        listener.recognitionException(e);

View Full Code Here

Examples of org.jostraca.comp.antlr.RecognitionException

    } 
    catch( StandardException se ) {
      throw se;
    }
    catch( TokenStreamRecognitionException tsre ) {
      RecognitionException re = tsre.recog;
      if( null != re ) {
        int    lineNumber = re.getLine();
        String line       = TextUtil.getLine( currentContent, lineNumber-1 ); 
        if( Standard.EMPTY == line ) {
          throw new TemplateParserException( TemplateParserException.CODE_syntax_error, re.getMessage() );
        }
        else {
          throw new TemplateParserException( TemplateParserException.CODE_syntax_error, line );
        }
      }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.