bin/166861: bsdgrep -E and sed handle invalid {} constructs strangely

[Jim Pryor]

The following reply was made to PR bin/166861; it has been noted by GNATS.

From: Jim Pryor <dubiousjim at gmail.com>
To: bug-followup at 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 at gmail.com