Re: pkg/33410: pkgsrc problem with posix awk

[Aleksey Cheusov <cheusov%tut.by@localhost>]

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

From: Aleksey Cheusov <cheusov%tut.by@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/33410: pkgsrc problem with posix awk
Date: Sat, 06 May 2006 13:43:57 +0300

 > The following reply was made to PR pkg/33410; it has been noted by GNATS.
 
 > From: joerg%britannica.bec.de@localhost
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: 
 > Subject: Re: pkg/33410: pkgsrc problem with posix awk
 > Date: Sat, 6 May 2006 10:13:31 +0200
 
 >  On Tue, May 02, 2006 at 09:30:05PM +0000, Roland Illig wrote:
  >>  And I prefer to do things right. Other implementations of awk may just 
  >>  continue without warning (the OpenGroup's web site is badly formatted, 
  >>  but I think it states undefined behavior for invalid programs), and can 
  >>  you tell what they do?
 >  
 >  The behaviour of this programs is actually quite well defined. the
 >  backslash escaping is not *necessary* in this situations, but it doesn't
 >  really hurt either.
 AFAIU susv3 defines the following backslashed symbols for ERE
 
 .[\()*+?{|^$
 
 but only the following for awk
 
 '"' '/' '\' '\a' '\b' '\f' '\n' '\r' '\t' '\v' and '\ooo'.
 
 -- 
 Best regards, Aleksey Cheusov.