[il-antlr-interest: 22186] Re: [antlr-interest] [antlr-dev] ANTLRWorks debugger

[Jim Idle]

Benjamin Niemann wrote: On Sat, Feb 28, 2009 at 9:44 PM, Filipe David Manana <fdman...@ieee.org> wrote: Holy cow! It works using port 49153 :| This gotta be one of the most mysterious things in the world! Port 49100 doesn't work, neither 50000, neither 49123, neither... This was something that confused me a bit as well, when I started implementing debug support for the Python target. The default port on the server side (the parser being debugged) is 49153, but AW defaults to 49100 in the 'Remote Debugger' dialog. Any reason for this discrepancy? We changed it in AW and the C runtime, but it did not change in ANTLR is the answer I think. We changed it because the original port clashed with something on Windows Vista. I meant to fix this before release and it slipped past. Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to il-antlr-interest@googlegroups.com To unsubscribe from this group, send email to il-antlr-interest+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en -~----------~----~----~----~------~----~------~--~---

List: http://www.antlr.org/mailman/listinfo/antlr-interest
Unsubscribe: 
http://www.antlr.org/mailman/options/antlr-interest/your-email-address