On May 6, 2009, at 10:41 AM, Yauhen Yakimovich wrote: > Greetings, > > I have good progress with PHP target runtime. Lexer, Parser generation > looks fine. Now I am working with AST generation and StringTemplate > porting.
cool :) > I have a few questions: > > 1) Is there any way to test if my runtime is in sync with v3? I mean > some bunch of unittests. gUnitTest doesn't seems to be of great help > here. > For now, my way is implementing different examples and checking if > everything works, but this is far from full feature list test. for now that's probably the best way. you can ask the dev list to see what they do. > What I mean is that I want to be sure that every template in XYZ.stg > generates proper functionality. > > 2) How can I commit the code to the trunk of the project? > > So far, I have little of .java code, but a lot of .stg and .php ok, do you have an account yet? Have you signed and emailed or faxed contrib agreement? http://www.antlr.org/doc/ANTLR-contributor-agreement.pdf > 3) Is there any way to make ingrammar {..} code generation process > dependable on target choice. Something like: > > .. > foo: > : BAR > { > <if target(Php)> > \$this->x = 1; > <elseif target(Java)> > x =1; > </if> > } > ; > .. There might be a language attribute...but I don't think we can test it's value...what do you need specifically? Naturally, the above isn't necessary as I have java templates and we don't want to merge with other targets. > > > 4) Please, subscribe me for the dev maillist. > done. > 5) Is phpDocumentor a fine choice for runtime API documentation or I > should definitely use doxygen? doxygen would be good as it's what the others use. You can use what you like though :) Ter _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
