Changes between Initial Version and Version 1 of Ticket #498, comment 5


Ignore:
Timestamp:
Dec 7, 2016, 2:14:13 PM (9 years ago)
Author:
Greg Couch

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #498, comment 5

    initial v1  
    11This bug looks like it is due to a change in grako 3.17: "Report the parse exception (grako.exceptions.!FailedParse) ocurring furthest in the input so error messages are more meningful even when no cut (~) expressions are used."
    22
    3 ChimeraX's AnnotationErrors expects the "pos" attribute to reflect how much input was successfully parsed before there was an error.  In this case, was the "red" successfully parsed or not?  From ChimeraX's point of view, it was not, it did not match an atomspec.  But grako did find a token.  Need to look at how atomspec parser works.
     3ChimeraX's !AnnotationErrors expects the "pos" attribute to reflect how much input was successfully parsed before there was an error.  In this case, was the "red" successfully parsed or not?  From ChimeraX's point of view, it was not, it did not match an atomspec.  But grako did find a token.  Need to look at how atomspec parser works.