Changeset 33639 in project


Ignore:
Timestamp:
09/11/16 16:20:57 (5 years ago)
Author:
sjamaan
Message:

Explain limitation in prcc regarding error handling

File:
1 edited

Legend:

Unmodified
Added
Removed
  • release/4/uri-generic/trunk/alternatives/README

    r33637 r33639  
    166166test suite.
    167167
     168Another disadvantage is that parse errors will always be written to
     169the current output port.  There seems to be no way to supply custom
     170error handling.  The error handling itself is pretty decent in that it
     171keeps track of input position and it knows what was expected when the
     172error occurred.  Unfortunately, for more complex parsers this doesn't
     173work perfectly: (parse-string "qux" (sel (str "foo") (str "bar")))
     174results in an error that says "bar was expected".  On the other hand,
     175this is easier to customize by using "act" with a custom failure
     176handler.
     177
    168178It's obviously too slow for real-world use, probably because it uses
    169179srfi-41 which is not known to be efficient at all.  It could probably
Note: See TracChangeset for help on using the changeset viewer.