From mboxrd@z Thu Jan 1 00:00:00 1970 References: <72381975.739900.1513623186634.ref@mail.yahoo.com> <72381975.739900.1513623186634@mail.yahoo.com> From: Zdenek Kabelac Message-ID: Date: Mon, 18 Dec 2017 23:43:57 +0100 MIME-Version: 1.0 In-Reply-To: <72381975.739900.1513623186634@mail.yahoo.com> Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [linux-lvm] lvm filter regex format Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: matthew patton , LVM general discussion and development Dne 18.12.2017 v 19:53 matthew patton napsal(a): >> =C2=A0 https://github.com/jthornber/lvm2-ejt/blob/master/libdm/regex/p= arse_rx.h > =20 > not to be ungrateful but why on earth would one NOT use the glibc standar= d regex library? Nobody cares about pointless optimization. Surprises like = "well, we only implemented most of the spec" are what drives people nuts! >=20 > I agree this particular length-based match is rather odd but there are pl= enty of useful examples I am sure that could benefit from {x,y} notation. Such code was actually written long time ago - but since the syntax of=20 standard glibc regex accepts slightly different strings - it would be an=20 incompatible change - so it's been considered now worth breaking the=20 compatibility at that time... Regards Zdenek