-
Notifications
You must be signed in to change notification settings - Fork 9
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
dash in range not correctly parsed #1
Comments
The error is also triggered for an empty range, e.g. ghci> ("1" =~ "[1-0]") :: String
"*** Exception: Explict error in module Text.Regex.TDFA.String : Text.Regex.TDFA.String died: parseRegex for Text.Regex.TDFA.String failed:"[1-0]" (line 1, column 4):
unexpected A dash is in the wrong place in a bracket
expecting "]"
CallStack (from HasCallStack):
error, called at lib/Text/Regex/TDFA/Common.hs:31:3 in regex-tdfa-1.3.1.3-inplace:Text.Regex.TDFA.Common I think the intention was to give another error in this case: regex-tdfa/lib/Text/Regex/TDFA/ReadRegex.hs Lines 130 to 137 in 85c89c9
However, this error is caught by <|> :regex-tdfa/lib/Text/Regex/TDFA/ReadRegex.hs Lines 118 to 119 in 85c89c9
So we end up with the error triggered by the last alternative: regex-tdfa/lib/Text/Regex/TDFA/ReadRegex.hs Lines 139 to 144 in 85c89c9
|
The solution to the OP is to simply not further restrict the appearance of regex-tdfa/lib/Text/Regex/TDFA/ReadRegex.hs Lines 141 to 143 in 85c89c9
|
There are no illegal occurrences of `-` in a bracket expression. Those that are separators of a range (e.g. `a-z`) are simply standing for themselves. A dash can even be an start or end point of a range, as in `[--@]`.
Ranges beginning with `-` were not recognized.
Ranges beginning with `-` were not recognized. Write GHC environment files so parallel-doctest picks up correct package.
### 1.3.2 _2022-07-18, Andreas Abel_ - Export `decodePatternSet` and `decodeCharacterClass` from `Text.Regex.TDFA.Pattern` ([#16](haskell-hvr/regex-tdfa#16)) - Extend and correct docs for `Pattern` module - Tested with GHC 7.4 - 9.4 ### 1.3.1.5 _2022-07-18, Andreas Abel_ - Allow dash (`-`) as start of a range, e.g. `[--z]` ([#1](haskell-hvr/regex-tdfa#1), [#45](haskell-hvr/regex-tdfa#45)) - Tested with GHC 7.4 - 9.4 ### 1.3.1.4 _2022-07-17, Andreas Abel_ - Fix parsing of dashes in bracket expressions, e.g. `[-a-z]` ([#1](haskell-hvr/regex-tdfa#1)) - Fix a deprecation warning except for on GHC 8.2 ([#21](haskell-hvr/regex-tdfa#21)) - Documentation: link `defaultComptOpt` to its definition ([#13](haskell-hvr/regex-tdfa#13)) - Verify documentation examples with new `doc-test` testsuite - Tested with GHC 7.4 - 9.4 ### 1.3.1.3 _2022-07-14, Andreas Abel_ - Fix an `undefined` in `Show PatternSet` ([#37](haskell-hvr/regex-tdfa#37)) - Document POSIX character classes (e.g. `[[:digit:]]`) in README - Tested with GHC 7.4 - 9.4 ### 1.3.1.2 Revision 1 _2022-05-25, Andreas Abel_ - Allow `base >= 4.17` (GHC 9.4) ### 1.3.1.2 _2022-02-19, Andreas Abel_ - No longer rely on the `MonadFail` instance for `ST` (future `base` library change, see [#29](haskell-hvr/regex-tdfa#29)). - Silence warning `incomplete-uni-patterns` (GHC >= 9.2). - Import from `Data.List` explicitly or qualified (warning `compat-unqualified-imports`). - Import from `Control.Monad` to allow `mtl-2.3` in its `rc3` incarnation.
ChrisKuklewicz/regex-tdfa#24, originally reported by @pjljvandelaar
As specified in
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html
However,
("@" =~ "[--@]")
results inThe text was updated successfully, but these errors were encountered: