From owner-freebsd-hackers@FreeBSD.ORG Mon May 9 06:13:35 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30C531065672; Mon, 9 May 2011 06:13:35 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8]) by mx1.freebsd.org (Postfix) with ESMTP id 160178FC17; Mon, 9 May 2011 06:13:34 +0000 (UTC) Received: from bitblocks.com (localhost [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id A62EAB827; Sun, 8 May 2011 23:13:34 -0700 (PDT) To: Zhihao Yuan In-reply-to: Your message of "Sun, 08 May 2011 21:35:04 CDT." References: <4DC7356C.20905@kovesdan.org> <20110509011709.5455CB827@mail.bitblocks.com> <4DC74546.1060902@kovesdan.org> <20110509014938.EE292B827@mail.bitblocks.com> Comments: In-reply-to Zhihao Yuan message dated "Sun, 08 May 2011 21:35:04 -0500." Date: Sun, 08 May 2011 23:13:34 -0700 From: Bakul Shah Message-Id: <20110509061334.A62EAB827@mail.bitblocks.com> Cc: Gabor Kovesdan , "Pedro F. Giffuni" , hackers@freebsd.org, Brooks Davis Subject: Re: [RFC] Replacing our regex implementation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 06:13:35 -0000 On Sun, 08 May 2011 21:35:04 CDT Zhihao Yuan wrote: > 1. This lib accepts many popular grammars (PCRE, POSIX, vim, etc.), > but it does not allow you to change the mode. > http://code.google.com/p/re2/source/browse/re2/re2.h The mode is decided when an RE2 object is instantiated so this is ok. You can certainly instantiate multiple objects with different options if so desired. > 2. It focuses on speed and features, not stability and standardization. Look at the open issues. Seems stable enough to me. re2 has a posix only mode. It also does unicode. > 3. It uses C++. We seldom accepts C++ code in base system, and does > not accept it in libc. This is the show stopper.