-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-deterministic state #28
Comments
Hi Isi, This can happen when there's more than one way to parse the input. It could be an issue with the grammar, or possibly an important element is missing from the input. For instance, many grammars have different On the other hand, suppose your grammar is not ambiguous. If the input doesn't have a value at all in the first You can debug this by printing each parse tree (hopefully there are only a few) and comparing them -- ideally you have a small number of trees, and only one of the parse trees is correct, and you can decide by looking at it. To print the parse trees, you can pass a Once you find the location where they diverge, look back at your grammar to see if you have overlapping constraints (like both segments share allowed values, but they should've been disjoint) or perhaps constraints are missing (like you have two reachable |
Hi Kyle, Adding this flag to For one of the sample files it never stops processing, no return, but luckily I got other files which process even though the output is very lenghty |
One of the segments did not have a ending marker i.e:
noticed SN1 does not have a line termination marker, that was causing the non-deterministic problems. Now, by having a proper of SN1 shouldn't it have handle this error ? basically the system was reading PCHL as one item yet the last SN1 field (E355) is defined as max 2 chars-- just asking to see if we can improve StupidEDI |
I have been studying the trees generated by I will refresh git w/ the latest need to take a break as I am not being productive (spent most of the day chasing these issues down w/o any luck) 👎 |
running
edi-pp
against the latest message I am defining (PS830
), I am getting the following outputAny ideas as of why?
The text was updated successfully, but these errors were encountered: