|
|
|
[
Permlink
| « Hide
]
Terence Parr - 10/Nov/06 03:01 PM
THis is no problem unless you don't want to include stringtemplate.jar when not using ST, right?
I believe that is the case. The circular dependency is likely to be ugly rather than fatal.
What this means is that at the moment, applications built in V3 would need to include: - antlr-3.XX.jar - stringtemplate.jar - antlr-2.XXX.jar (since StringTemplate is built with ANTLR 2.x) If they don't use StringTemplate (as many don't), that is a real pain. Does RuleReturnScope really *need* that typed attribute? You are correct. THe dependency is odious. :( I guess we could use Object. ANTLR can generate a cast I guess for people using $a.st. Does that make sense?
Removed getTree and getTemplate from rule return. Don't need them. Only added them because I needed to get result trees/st's from rule return objects in my toTemplateList() or whatever, but I've removed those methods. Don't need this stuff anymore.
and unfortunately I need getTemplate in there too, but made it return Object.
|
|||||||||||||||||||||||||||||||||||||||