Quantifiers. Complete support for ranges: ++?? {2, 4}; ##?? {2} or {4}; ...
#7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* `++??` (2 - 4) * `+???` (1 - 4) * `+++?` (3 - 4) * `+?` (1 - 2) etc.
* `##??` (2 | 4) * `#???` (1 | 4) * `###?` (3 | 4) * `#?` (1 | 2) etc. See tests. Part of #7
|
MS & Quantifiers; new samples
3F
changed the title
++?? {2, 4}; ##?? {2} or {4}; ...++?? {2, 4}; ##?? {2} or {4}; ...
3F
added a commit
that referenced
this pull request
Aug 10, 2020
* NEW: Quantifiers are now standardized as follows:
https://github.com/3F/regXwild#-quantifiers
regex | regXwild | n
----------------|------------|---------
.\* | \* | 0+
.+ | + | 1+
.? | ? | 0; 1
.{1} | # | 1
.{2} | ## | 2
.{2, } | ++ | 2+
.{0, 2} | ?? | 0 - 2
.{2, 4} | ++?? | 2 - 4
(?:.{2}\|.{4}) | ##?? | 2; 4
.{3, 4} | +++? | 3 - 4
(?:.{1}\|.{3}) | #?? | 1; 3
* NEW: Second-order Quantifiers. Added support for `++`
regex equivalent `.{n, }`
* NEW: Quantifiers. Implemented `++??` support for ranges. Part of PR #7.
```
{n, m} where n > 0 and m > n
n == +
m == ?
```
* `++??` (2 - 4)
* `+???` (1 - 4)
* `+++?` (3 - 4)
* `+?` (1 - 2)
etc. See unit-tests.
* NEW: Quantifiers. Implemented `##??` support for ranges. Part of PR #7.
```
{n, m} where n > 0 and m > n
n == #
m == ?
```
* `##??` (2 | 4)
* `#???` (1 | 4)
* `###?` (3 | 4)
* `#?` (1 | 2)
etc. See unit-tests.
* FIXED: Fixed rewind in MS-split `|` like for '##'|'####'
* FIXED: Fixed errors in second order quantifiers: `?? == .{0, 2}` and `## == .{2}`
For example:
* False positive matching `[1####_of` for `TV_[11_of_24]`
* Crashed `number = '????';` for `number = '123';`
* and related.
* CHANGED: API versionString() marked as obsolete due to RXWVersion.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since we have only this today (
++after 86f0be1):and similar.
This PR will finally add complete support for (n, m) ranges 👇
✔ ++??
Andd2fb0b6++??(2 - 4)+???(1 - 4)+++?(3 - 4)+?(1 - 2)✔ ##??
Ora421443##??(2 | 4)#???(1 | 4)###?(3 | 4)#?(1 | 2)