From owner-freebsd-current@FreeBSD.ORG Tue Oct 24 15:35:33 2006 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EDA716A407; Tue, 24 Oct 2006 15:35:33 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4E3F43D66; Tue, 24 Oct 2006 15:35:32 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.8/8.13.8) with ESMTP id k9OFZNwY073717; Tue, 24 Oct 2006 19:35:23 +0400 (MSD) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.8/8.13.8/Submit) id k9OFZNVU073716; Tue, 24 Oct 2006 19:35:23 +0400 (MSD) (envelope-from ache) Date: Tue, 24 Oct 2006 19:35:23 +0400 From: Andrey Chernov To: Mikhail Teterin Message-ID: <20061024153523.GA73555@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Mikhail Teterin , Mikhail Teterin , current@FreeBSD.ORG, tjr@FreeBSD.ORG References: <200609202304.25537@aldan> <200609261302.40964.mi+mx@aldan.algebra.com> <20060926184447.GA17862@nagual.pp.ru> <200610240749.11234@aldan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200610240749.11234@aldan> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Mikhail Teterin , current@FreeBSD.ORG, tjr@FreeBSD.ORG Subject: Re: replacing FreeBSD's -lgnuregex with GNUlib's version X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 15:35:33 -0000 On Tue, Oct 24, 2006 at 07:49:10AM -0400, Mikhail Teterin wrote: > = Someone must test its compatibility with GNU regex and understand in > = details nature of their changes/fixes/differences. Without this work we > = can't blindly replace stable code with unknown one just for reason it is > = actively maintained. > > What kind of test would be deemed sufficient? I don't have anything at hand, but I saw a tests in some regex implementations I don't remember now. Perhaps someone else knows good regex test suits? The common bottle neck is locale: collating, multibyte and character classes handling. I can test it excepting multibyte, our multibyte-enabled developers needed. What must be tested before as primary target: general POSIX compatibility. What must be tested in second: GNU regex compatibility. -- http://ache.pp.ru/