[antlr-interest] C target: overriding parser and lexer error handlers

[Jim Idle]

Actually it looks like an error in the doxygen file that is causing the
apidocs to cut short.

Jim

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> bounces at antlr.org] On Behalf Of Vlad Roubtsov
> Sent: Wednesday, July 20, 2011 5:59 PM
> To: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] C target: overriding parser and lexer
> error handlers
>
> I think can answer my own question: there is a reference to apifuncs at
> http://antlr.org/api/C/group__apistructures.html (but not at
> http://www.antlr.org/api/C/atsections.html).
>
> On Wed, Jul 20, 2011 at 7:25 PM, Vlad Roubtsov
> <vlad at demoninsight.com>wrote:
>
> > Greetings,
> >
> > I am new to ANTLR but have extensive experience with JavaCC. With
> some
> > difficulty (section '@apifuncs' does not appear to be documented but
> > was mentioned in this list) I can intercept parser errors with my own
> > implementation of displayRecognitionError():
> >
> > @parser::apifuncs
> > {
> >     RECOGNIZER->displayRecognitionError = <my parser error function>;
> > }
> >
> > However, lexer errors continued to cause messages to be printed to
> stderr.
> > After some more poking around the source code the following seemed to
> work:
> >
> > @lexer::apifuncs
> > {
> >     LEXER->rec->displayRecognitionError = <my lexer error function>;
> }
> >
> > My question: are these @(lexer|parser)::apifuncs section declarations
> > the supported way to do this? (@members does not work).
> >
> > Thank you,
> > Vlad
> >
>
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-
> email-address