[antlr-interest] Resetting an AST tree walker
Steve Souza
steve at stevesouza.com
Wed Apr 22 20:17:23 PDT 2009
<<I don't like this at all, but I believe in the thread that you cited
earlier someone says it is the intended behaviour.>>
I wonder what the logic is there. One of the big benefits of a tree walker
is to be able to repeatedly walk the nodes. I hope they don't remove that
capability from the BufferedTreeNodeStream. Did that one work for you?
Except for increased memory is there ever a reason not to use
BufferedTreeNodeStream instead of CommonTreeNodeStream?
On Wed, Apr 22, 2009 at 11:04 PM, Michael Bedward <michael.bedward at gmail.com
> wrote:
> Hi Steve,
>
> > I would think CommonTreeNodeStream should work however, so it
> > seems like a bug.
>
> but as I tried to explain, the new behaviour of CommonTreeNodeStream
> is that its contents are discarded as they are accessed by the tree
> walker, so you can reset the stream but there's nothing there anymore
> !
>
> I don't like this at all, but I believe in the thread that you cited
> earlier someone says it is the intended behaviour.
>
> Michael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.antlr.org/pipermail/antlr-interest/attachments/20090422/1bfd54e5/attachment.html
More information about the antlr-interest
mailing list