Classlib: Patterns: Pn should set flag at onset #2833
Merged
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.
From the discussion of Pn/Pgate on sc-users, I found a little bug.
Pn's help implies that it sets the flag every time the subpattern starts. But it doesn't do this for the first repeat. Pn's logic "cheats" and sets after the pattern, not at the beginning. This has an unintended consequence: an immediately following Pn does not trigger a new value in Pgate.
After this change, the second Pn does trigger a new duration value.