#26 Wrong ParseError in some special cases

closed-fixed
nobody
None
2
2009-01-16
2008-09-18
Eike Welk
No

Under certain special conditions a parser does not recognize legitimate input and instead raises a parse error.

To provoke the error one needs:
- to use setResultsName frequently.
- an own class to replace ParseResult. This class needs a __getitem__ method.
- some bad luck.

The attached script demonstrates the bug.

This a very obscure bug, and it can be quite easily worked around. So this bug does not need a high priority, however it confused me quite a bit.

Discussion

  • Eike Welk

    Eike Welk - 2008-10-29
    • priority: 5 --> 2
     
  • Paul McGuire

    Paul McGuire - 2008-12-20

    Obscure, perhaps, but fixable nonetheless.

    Thanks for posting this, I'll have a fixed version in SVN shortly.

    -- Paul

     
  • Paul McGuire

    Paul McGuire - 2008-12-20
    • status: open --> pending
     
  • Paul McGuire

    Paul McGuire - 2008-12-20
    • status: pending --> pending-fixed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks