From owner-freebsd-bugs  Wed Sep  6 17:33:09 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.11/8.6.6) id RAA00374
          for bugs-outgoing; Wed, 6 Sep 1995 17:33:09 -0700
Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11])
          by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id RAA00368
          for <freebsd-bugs@freefall.FreeBSD.org>; Wed, 6 Sep 1995 17:33:07 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by wcarchive.cdrom.com (8.6.11/8.6.9) with ESMTP id RAA02805 for <freebsd-bugs@wcarchive.cdrom.com>; Wed, 6 Sep 1995 17:35:07 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA08719; Thu, 7 Sep 1995 10:30:35 +1000
Date: Thu, 7 Sep 1995 10:30:35 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199509070030.KAA08719@godzilla.zeta.org.au>
To: freebsd-bugs@wcarchive.cdrom.com, hobbit@avian.org
Subject: Re: sed bug?
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>I have stumbled across an inconsistency in FreeBSD 'sed'.  On every other
>platform I have access to, the regex `/[/|]/' to mean "slash or pipe" is valid,
>but the FreeBSD version errors out on this.  Trying to quote the embedded
>slash, a la `/[\/|]/', avoids the error, but that breaks on other systems
>that match on `\` as well.  One or the other is clearly wrong.

This was fixed in 2.2-current on Aug 16 and in 2.1 on Aug 26.

Bruce