From fb332fa541cacb201d0cb4f7b767b9c20ca1f024 Mon Sep 17 00:00:00 2001 From: Ralf Wildenhues Date: Tue, 22 Sep 2009 07:36:04 +0200 Subject: [PATCH] Clarify documentation about Solaris sed quantifier restriction. * doc/autoconf.texi (Limitations of Usual Tools) : '*' does not work after subexpressions, \{M,N\} only after one-character expressions. From GCC PR 38923. Signed-off-by: Ralf Wildenhues --- ChangeLog | 7 +++++++ doc/autoconf.texi | 8 +++++--- 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 6b338d07..d3443f7b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,10 @@ +2009-09-22 Ralf Wildenhues + + Clarify documentation about Solaris sed quantifier restriction. + * doc/autoconf.texi (Limitations of Usual Tools) : '*' does + not work after subexpressions, \{M,N\} only after one-character + expressions. From GCC PR 38923. + 2009-09-21 Eric Blake Fit configure output in 80 columns. diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 53fab23e..4032b9c1 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -17967,9 +17967,11 @@ Nested parentheses in patterns (e.g., @samp{\(\(a*\)b*)\)}) are quite portable to current hosts, but was not supported by some ancient @command{sed} implementations like SVR3. -Some @command{sed} implementations, e.g., Solaris, -restrict the special role of the asterisk to one-character regular expressions. -This may lead to unexpected behavior: +Some @command{sed} implementations, e.g., Solaris, restrict the special +role of the asterisk @samp{*} to one-character regular expressions and +back-references, and the special role of interval expressions +@samp{\@{@var{m}\@}}, @samp{\@{@var{m},\@}}, or @samp{\@{@var{m},@var{n}\@}} +to one-character regular expressions. This may lead to unexpected behavior: @example $ @kbd{echo '1*23*4' | /usr/bin/sed 's/\(.\)*/x/g'} -- 2.47.2