hiya!  added

http://www.antlr.org/wiki/display/~admin/ANTLR+v4+plans

so we can plan ahead and track a wish list.

> Building ANTLR-centric tools is a pain with the v2 grammars, let me tell you. 
> So I regard the transition to v3 in v3 (or is that v4 in v4) as the most 
> critical point, aside from the weird v2 language.
> BTW it is the same for ST3 being based on v2, which makes it really icky to 
> build tools on top of it. What I've come to realize is that development tools 
> make all the difference, both in producing and maintaining code.
> Essentially, if we want better adoption, we must provide an easy path for 
> tools devs.

yeah, we need to cut loose v2.

>> * While I tried to do as much re-factoring as possible while developing 
>> ANTLR v3, most of it was tactical. At some point, strategic re-factoring 
>> (rewriting whole sections or all) becomes necessary. For example, I 
>> literally had to jam grammar composition into the tool, leaving it fragile. 
>> It's becoming hard to fix things and add new features. A lot of the current 
>> features have been added while writing the first and second books. Doing so 
>> simultaneously was valuable from a feature and functionality point of view, 
>> but not from a code cleanliness point of view.
> 
> Every time I look at the tool code I cringe, to be honest. It's huge (for 
> what it does) and at times I can't help thinking that it

21k lines ain't *that* bad really. it's a pretty dang complicated problem, 
especially with composites etc...  it *is* dark and scary inside though :(

>> * I have some important new features such as the better expression grammar 
>> stuff that would be inconvenient to implement in the current code base.
> 
> And incremental parsing ;)

Hmm...incr parsing is easy. incr lexing is not.

> - Change to make it OSGi-friendly (the tool I mean).


I just scanned the pages for OSGi.  uh, what the hell is it? ;)  What would you 
need?

Ter

_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org/mailman/listinfo/antlr-dev

Reply via email to