You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and input the string "foo\n..........", then packcc will read 8 bytes for this rule when it really only needed to read 4.
As an example of where this is a problem, consider an interactive parser where the user enters data line by line, if the user types "foo\n", the parser will request two or more lines of input from the user when only one was actually needed.
The text was updated successfully, but these errors were encountered:
That's a good suggestion but maybe does not work for more complicated grammars where such interactions are less obvious.
In the end I have rewritten my code to buffer lines before passing it to the parser after a known terminator, this issue no longer affects me, I don't mind closing it.
If you have a grammar like:
and input the string "foo\n..........", then packcc will read 8 bytes for this rule when it really only needed to read 4.
As an example of where this is a problem, consider an interactive parser where the user enters data line by line, if the user types "foo\n", the parser will request two or more lines of input from the user when only one was actually needed.
The text was updated successfully, but these errors were encountered: