Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [Dltk-dev] Documentation?

  well - what do you mean by integrate?

  i tried to write an antlr parser for perl and gave up for a different route, but what i did learn was this:

 if all you built was a lexer, then you need to walk the tokens yourself and ultimately construct a ModuleDeclaration object. if you built a parser as well, then you should be able to work in the construction of the ModuleDeclaration directly into that implementation.

  look at the parse method in the PythonSourceParser - from there you can see where the python parser hooks in.

  hope that helps some

On 7/8/07, Mark Mandel <mark.mandel@xxxxxxxxx> wrote:
Thanks for the heads up...

I'm trying to work through the Python example, as they both use an
ANTLR grammer (tho the example they give is ANTLR 2.7, whereas I'm
using 3.0)...

I'm struggling to work out how to take my ANTLR parser and integrate
it with the dltk parser... there seems to be a fair amount of work on
top to get things going in that area.

I'm going to keep plugging through the python example, but if anyone
has any direction to take on where to look for these details, please
let me know,

On 7/9/07, Jae Gangemi <jgangemi@xxxxxxxxx> wrote:
>   that sounds pretty cool. i've been developing against the source head
> since i'm still pretty far off from a release (it also allows me to submit
> things back as well) - once i get closer to a release, i'll worry about
> tying myself to a release.
>   feel free to peruse my source as well for another example
> ( - the parser isn't
> gonna work for you if you try to run it b/c you'll need some extra perl
> modules installed, and it's tied to concrete script paths, my next cleanup
> todo) - but all good otherwise. :)
>   if anyone is interested in devoting some cycles to a perl plugin, do let
> me know :)

E: mark.mandel@xxxxxxxxx
dltk-dev mailing list


Back to the top