The described problem is fixed. However, Gabi was experimenting with some other
wrong planner calls and observed some strange behaviour for "--search
astar()(lmcut)".
With my fix, this yields the error message "misplaced opening bracket ( at:
pseudoroot", which does not really describe the problem too good.
Before my fix the planner does not complain but runs astar with the lmcut
heuristic. (This happened because the parser only generates a new node when we
have some text in the buffer before a "(" occurs. It will however in any case go
to the last child of the node it currently points at if a "(" occurs. So if we
had already a child at the current it will just go to this child (in the
previous example astar) or if we don't have a child at this point, it will throw
a segmentation fault.)
While fixing the bug I added an additional if statement to catch the case of an
opening bracket without any text in the buffer where the parser throws a
ParseError. ParseError only has a constructor which accepts a string and a Node
of the parse tree, thus I can only output an error message indicating on which
node of the tree the error occurred. As mentioned before this is, depending on
the situation, not very helpful (especially when the node is "pseudoroot").
My idea would be that we also indicate at which position in the text the error
occurs (something like "error occured after 'search astar()'").
|