Message-ID: <39972C2F.13040963@Shevchenko.Kiev.UA> Date: Mon, 14 Aug 2000 02:15:59 +0300 From: Ruslan Shevchenko X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Paul Eggert CC: meyering AT ascend DOT com, eliz AT is DOT elta DOT co DOT il, tr AT eth DOT net, djgpp-workers AT delorie DOT com, autoconf AT gnu DOT org Subject: Re: portability of sed's \{0,1\}? References: <200008110941 DOT CAA29407 AT drawbridge DOT ascend DOT com> <200008111728 DOT KAA12810 AT drawbridge DOT ascend DOT com> <200008111956 DOT MAA12359 AT ruby DOT twinsun DOT com> <200008130629 DOT XAA17773 AT green-office DOT twinsun DOT com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Paul Eggert wrote: > From: Jim Meyering > Date: 12 Aug 2000 09:47:59 +0200 > > Thanks, but if no one can point to an actual system for which > sed's \{m,n\} doesn't work, I'm going to document it as portable. > > The sed FAQ, version 014 says: > > * Ultrix 4.3 sed doesn't support \(...\)\{...\} (the idiom used here). > * Likewise for HHsed v1.5 (by Howard Helman). > * sedmod v1.0 (by Hern Chen) doesn't support \{...\} at all. > > (Granted, these are marginal targets these days. I vaguely recall that > someone has a bug-fix-only 4.3BSD VAX on the net somewhere in Russia, > with guest accounts. Would that count? :-) > Why still supports ultrix-es ? > > Perhaps the autoconf programming-style section should mention the sed FAQ.