'[ <aml> ]' syntax has stunted error location report
Closed this issue · 1 comments
This issue does not affect general use cases by end-users. It is a focus on helping end-user identifying their parse error scenarios ... related to AML syntaxes.
Whenever a syntax error occurs within the address_match_list (aka <aml>) syntax, it always reports the location of the text offset as the beginning of AML and not where the actual offending character occurs.
For example,
deny-answer-address { 127.0.0.1 }; is missing a semicolon after 127.0.0.1 but error code will report error offset location as 0 (zero), when it should be 32.
Until this is fixed, many development of new keywords using AML syntax will be long and audurously difficult to create those newly definitions of PyParsing logic/rule set ... that are re-using <aml> syntax.
It should be noted that <aml> is a recursive syntax.