Correctly parse statements with multiple escaped characters #292
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: Statements such as
foo\(\)
were not being correctly parsed, see #291.Solution: Whenever a character is read by a
WordIterator
when theBACKSL
flag is set, the flag gets unset.Changes introduced by this pull request:
Drawbacks:
WordIterator
beyond parsing command line statements.Fixes: Resolves #291.
State: Ready with the caveat of adding more unit / regression tests, also formatting and such.