X-Authentication-Warning: ixi.eng.ascend.com: meyering set sender to meyering AT ascend DOT com using -f Sender: meyering AT ascend DOT com To: Paul Eggert Cc: 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> From: Jim Meyering In-Reply-To: Paul Eggert's message of "Fri, 11 Aug 2000 12:56:20 -0700 (PDT)" Date: 12 Aug 2000 09:47:59 +0200 Message-ID: Lines: 14 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.6.92 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Reply-To: djgpp-workers AT delorie DOT com Paul Eggert writes: | From: Jim Meyering | Date: 11 Aug 2000 20:11:25 +0200 | | I saw the earlier thread (on the autoconf list) on this topic where | someone found that `?' and \| were not portable. Has anyone found a | system on which \{m,n\} is not portable? | | Most likely, seds that don't support ? and \| also don't support | \{m,n\}, as I recall that those features were introduced to USG Unix | at about the same time. Unix Version 7 didn't have them. 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.