Home | Download | ANTLRWorks | Wiki | About ANTLR | Feedback | Support | Bugs | v2


Latest version is 3.0.1
Download now! »

Download
» Home
» Download
» ANTLRWorks
» News
»Using ANTLR
» Documentation
» FAQ
» Articles
» Grammars
» File Sharing
» Runtime API
» Tech Support
» Bug Tracking
»About ANTLR
» What is ANTLR
» Why use ANTLR
» Showcase
» Testimonials
» Getting Started
» Software License
» ANTLR WebLogs
» ANTLR Workshops
»StringTemplate
»ANTLR v2
»Feedback
»Credits
»Contact


Support StringTemplate, ANTLR Project by making a donation! Terence often pays for things like the antlr.org server, conference travel, and this site design (that alone cost US$1000). Buy him a beer and pizza remotely ;)

Search



Stuff I do not like in ANTLR 3 prototype

RSS Feed
The stateCounter is not thread safe and I have to set it in weird external ways when testing and such. Perhaps make a state number for testing as well as one for other stuff.

I wonder about the names of Node, Graph etc... Do I need DFANode as separate than NFANode? Should it be DFAState and NFAState not node?

What about BitSet vs LSet? Why have both?

Should we hook up states pointing to each other with pointers or should we store int indexes into a numberToState table and deference via the array to get to an actual node?

Make args (DFANode vs IntArrayList) more consistent in NFA->DFA conversion routines.