Occasionally, parsley can throw an error from within an instruction execution. There are three main sources for this to occur within:
An error within a user-defined function called from inside a parser
An out of scope reference being polled after unsafe initialisation
A legitimate bug in parsley
It would be good to try and distinguish between these, where possible, and catch any exceptions generated within the parser. These can be rethrown from outside the parsing context, removing any noise for user-made errors, report likely causes from undefined behaviour within parsley, and otherwise provide a more useful and detailed diagnostic for me that can be used in a bug report.
Occasionally,
parsleycan throw an error from within an instruction execution. There are three main sources for this to occur within:parsleyIt would be good to try and distinguish between these, where possible, and catch any exceptions generated within the parser. These can be rethrown from outside the parsing context, removing any noise for user-made errors, report likely causes from undefined behaviour within
parsley, and otherwise provide a more useful and detailed diagnostic for me that can be used in a bug report.