Date: Wed, 02 Jul 2014 16:21:42 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Pedro Giffuni <pfg@freebsd.org> Cc: freebsd-standards@FreeBSD.org Subject: Re: regex(3): support for \< and \> word delimiters Message-ID: <53B477E6.10103@FreeBSD.org> In-Reply-To: <20545470-A847-4835-A42B-382E5CC363ED@freebsd.org> References: <53556919.4010305@freebsd.org> <53ADD32C.5040503@FreeBSD.org> <20545470-A847-4835-A42B-382E5CC363ED@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Barc27AgSlAMftbldr21qPgcJWdxtWPxG Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 6/27/2014 4:15 PM, Pedro Giffuni wrote: > Hi; >=20 > Il giorno 27/giu/2014, alle ore 15:25, Bryan Drewery <bdrewery@FreeBSD.= org> ha scritto: >=20 >> On 4/21/2014 1:53 PM, Pedro Giffuni wrote: >>> Hello; >>> >>> Is there any related standard (or in absence strong feelings) >>> about having \< and \> delimiters in regex expressions? >>> >>> I have an old PR bin/153257 which actually comes from illumos: >>> https://www.illumos.org/issues/516 >>> >>> I don't use them but maybe it would help people moving their >>> scripts from Solaris. >>> >>> Regards, >>> >>> Pedro. >> >> I don't know about a standard, but I find the lack of \< \> to be a >> frustrating difference with other platforms. [[:<:]] [[:>:]] work but >> are far more characters to type. >> >=20 > Thank you for the feedback! I had closed the issue because I thought th= ere was no interest. >=20 > Another thing that needed consideration was that I thought there was so= me work going on to replace libregex with libtre, which doesn=92t support= *any* such delimiter so committing the change would raise the bar for th= e replacement. Discussing it with Gabor it seems like libtre is not in th= e capacity of replacing our current libregex anyways so I guess Spencer=92= s libregex is here to stay. >=20 > While here, there is also the sed(1) syntax issue: >=20 > https://www.illumos.org/issues/586 >=20 > Adopting both changes would probably reduce to a minimum the use of GNU= sed in the ports tree, but such changes are likely to be controversial(?= ) and I don=92t feel like wearing asbestos underwear at this time .. at l= east not for sed ;). >=20 > Pedro. >=20 IMHO yes that is a good thing to bring over as it helps with people coming from other platforms and improves portability with scripts. I started on Linux and kept wondering why I had FILEe files all over my system until I realized -i '' was required on FreeBSD. --=20 Regards, Bryan Drewery --Barc27AgSlAMftbldr21qPgcJWdxtWPxG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTtHfmAAoJEDXXcbtuRpfPXKYIAJo4jmqGDTwIa8/y3F9JYUa2 4h2hpveUU+q1q5jND/Gx8ItKr2qQBGdXfI0AX3E5V5y9rubAgt/oXmtL6n7p7b+M bQ+XDWdA3jIGm4TUXnpgcz32zLSysSDW5U661UxH/n2TEoQpZTOaLWZ7Q/pme33/ LTuSyadoOMrRVa4qTo0jz+4Tjv3++yExKL8MXdDoCRNJgTRkLf4kmrJh3hxMlFxg I4IwuaJ4ArVNtZJBk/jBGMVN7vg5L/QyTzp1xsUNuPFok1NwXKjWiV5p+4kJXYmu y2i+RR3Bwz+4kgq/m7I83/lMMWEf0H4h4VGBwnYhnrKtB6Y1kRXyzT+MFMIZiig= =ymDB -----END PGP SIGNATURE----- --Barc27AgSlAMftbldr21qPgcJWdxtWPxG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53B477E6.10103>