Date: Wed, 11 Apr 2012 23:50:15 GMT
From: Jim Pryor <dubiousjim@gmail.com>
To: freebsd-bugs@FreeBSD.org
Subject: Re: bin/166861: bsdgrep -E and sed handle invalid {} constructs strangely
Message-ID: <201204112350.q3BNoFiE024660@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/166861; it has been noted by GNATS.
From: Jim Pryor <dubiousjim@gmail.com>
To: bug-followup@FreeBSD.org
Cc:
Subject: Re: bin/166861: bsdgrep -E and sed handle invalid {} constructs
strangely
Date: Wed, 11 Apr 2012 19:45:57 -0400
(5) FreeBSD sed without -r, as well as the other sed implementations,
reject unmatched \( and unmatched \) both as invalid patterns. So too do
all these grep implementations without -E.
Similarly, gnu sed with -r rejects unmatched ( and unmatched ) both as
invalid patterns. And so too do all these egrep implementations.
Like everyone else, FreeBSD sed with -r rejects unmatched ( as invalid.
But it diverges in treating unmatched ) as literal.
--
dubiousjim@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204112350.q3BNoFiE024660>