[antlr-interest] v3.0 debug interface

[Scott Stanchfield]

The server starting part is the trouble. You can set up eclipse to start a
plugin on startup, though, which would take care of it. However, if there's
already a server running, we'd need to pick a different port, and the server
needs the right classpath.

It's a bit of a pain... But not *too* bad

-- Scott 

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org 
> [mailto:antlr-interest-bounces at antlr.org] On Behalf Of Terence Parr
> Sent: Friday, March 25, 2005 2:10 PM
> To: 'antlr-interest'
> Subject: Re: [antlr-interest] v3.0 debug interface
> 
> 
> On Mar 24, 2005, at 8:25 PM, Scott Stanchfield wrote:
> 
> >>> That said, an implementation in Eclipse would need to use
> >> socket-based
> >>> communication ;)
> >>
> >> Really?  Oh well; good to know.
> >
> > Considering that the plugin would be running in a different VM than 
> > the application doing the parsing... Then again, we could 
> set up the 
> > launcher to run it in the same VM as eclipse, but that's 
> not generally 
> > a good idea b/c you then inherit the classpath of the eclipse 
> > installation rather than what's set up in the project.
> 
> Yeah, I forgot about the classpath issue.  :(  How easy is 
> the RMI stuff?  Does it automatically start up a light server 
> to handle the method calls (for Java only stuff)?
> 
> Ter
> --
> CS Professor & Grad Director, University of San Francisco 
> Creator, ANTLR Parser Generator, http://www.antlr.org 
> Cofounder, http://www.jguru.com
> 
>