diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2022-05-24 16:14:12 -0700 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2022-05-24 17:46:39 -0700 |
| commit | 15466174352557a5f9993aba8afb0cf9397b5b2c (patch) | |
| tree | 32402dc582a72caa5052e239a4bb3a30775d65ad /NEWS | |
| parent | 8e0c90966da12c25689c662515731af3c7177d99 (diff) | |
| download | grep-15466174352557a5f9993aba8afb0cf9397b5b2c.tar.gz | |
grep: warn about ‘(+x)’ etc.
These expressions are not portable and don’t always work as
expected, so warn about them. For example, “grep -E '(+)'”
doesn’t act like “grep '\(\+\)'”.
* src/dfasearch.c (GEAcompile): Warn about a repetition op at the
start of a regular expression or subexpression, except for ‘*’ in
BREs which is portable.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -14,7 +14,10 @@ GNU grep NEWS -*- outline -*- Regular expressions with stray backslashes now cause warnings, as their unspecified behavior can lead to unexpected results. For example, '\a' and 'a' are not always equivalent - <https://bugs.gnu.org/39768>. The warnings are intended as a + <https://bugs.gnu.org/39768>. Similarly, regular expressions or + subexpressions that start with a repetition operator now also cause + warnings due to their unspecified behavior; for example, *a(+b|{1}c) + now has three reasons to warn. The warnings are intended as a transition aid; they are likely to be errors in future releases. Regular expressions like [:space:] are now errors even if |