[antlr-interest] antlr 3.1b1 problems with DebugEventSocketProxy?

[Doucette, Charles]

I'm actually not trying to debug them per-se.
I did create a separate copy of my grammar which has no parameters, return types, or actions.
I was able to try debugging in Antlrworks with that copy of my grammar.

Now that my grammar appears ok, I am simply trying to test the entire parser.
I suspect the only thing that may need tweaking are my user defined actions.

Does the Antlr generator produce a debug parser by default?
I've only been using the default options.

Chuck

> -----Original Message-----
> From: Gavin Lambert [mailto:antlr at mirality.co.nz]
> Sent: Monday, June 02, 2008 5:37 PM
> To: Doucette, Charles
> Cc: antlr-interest Interest
> Subject: Re: [antlr-interest] antlr 3.1b1 problems with
> DebugEventSocketProxy?
>
> At 08:31 3/06/2008, Doucette, Charles wrote:
>  >For the time being, I have reverted to the current/earlier
> version  >of Antlr (i.e. 3.0.1 vs. 3.1b1).
>  >
>  >Is not being able to run multiple parsers a new restriction?
>  >If so, is that configurable?
>  >This may impact the code that I am developing.
>
> You can (and always have been able to) run multiple parsers
> at once, but if they're debug parsers (which appears to be
> the case from your mail) then you must set a unique port
> number for each one.  You'll also need multiple copies of
> ANTLRworks running if you need to debug them interleaved.
>
> Debugging multiple parsers simultaneously is bound to make
> your head hurt, though, so I'm not sure if that's really what
> you were trying to do.
>
>