Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 504971036E for ; Mon, 9 Feb 2015 18:36:33 +0000 (UTC) Received: (qmail 1643 invoked by uid 500); 9 Feb 2015 18:36:32 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 1496 invoked by uid 500); 9 Feb 2015 18:36:32 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 1483 invoked by uid 99); 9 Feb 2015 18:36:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 18:36:32 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of sjr@jdns.org) Received: from [209.85.212.175] (HELO mail-wi0-f175.google.com) (209.85.212.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 18:36:06 +0000 Received: by mail-wi0-f175.google.com with SMTP id r20so3183973wiv.2 for ; Mon, 09 Feb 2015 10:36:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=pohwI37tRgdt6tbFEA8ZI8AVuY4BGfZ6U0I6LaORmP4=; b=ZcixlBWb365xNr4B8RrvGFaM2jEzAXg5ZeKgyi7WjGNcAvdeCjpghMQmAXq/cCnTqR FIdQgY6gIqlKgJFMPzNSje4OPAoRmSq626QSceE1z1+xbG+GaLt9cuGu+9VPaghsHVs8 58gvxt7Kida7thPBMX/QQr5WgrfCshZxeNLylJg8jBail87eVkiw5dxR1jHRzj/A8SSI tCxV4JCw2Hk802966n3rQ1KaaJrInO2a9Aoex2mDUwvL6toq1DuSda2o8F1grDkcXJpZ v6W+UXJF0b7Htr/H3JS3AAE1pUjckKMyiHE0sjw19ibl8pkkgHNlHlubPcofOb5VmXgP vXpw== X-Gm-Message-State: ALoCoQn3KJShX0fgL4t0hQPhZDpxeL9LI3eRzdXxngfS9g0tUM96SM9IUMzH6GDv+AfLXhGi/NaO MIME-Version: 1.0 X-Received: by 10.194.84.176 with SMTP id a16mr42606452wjz.113.1423506964999; Mon, 09 Feb 2015 10:36:04 -0800 (PST) Received: by 10.27.228.198 with HTTP; Mon, 9 Feb 2015 10:36:04 -0800 (PST) In-Reply-To: References: <54CF2AA5.8050706@gmail.com> <54D0068C.8060603@gmail.com> <54D07B35.5060100@gmail.com> Date: Mon, 9 Feb 2015 10:36:04 -0800 Message-ID: Subject: Re: Anyone interested in regular expressions, again? From: James Ring To: Commons Developers List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org I'm working to bring re2j into the open, it will take some time because Google's internal procedures for this kind of thing are pretty lengthy. I'm hopeful it could be done in the next month or so. On Tue, Feb 3, 2015 at 12:14 PM, Benson Margulies wrote: > On Tue, Feb 3, 2015 at 2:39 AM, Thomas Neidhart > wrote: >> On 02/03/2015 01:46 AM, Benson Margulies wrote: >>> The irony here is that the Java HSRE port happened because it seemed >>> easier than an RE2 port. Note the same statements about API's pretty >>> much apply. >> >> I am sorry, my response was not very sensible wrt your original proposal. > > It seems very sensible to me. A team at Google producing re2j is > likely to have produced a far superior comestible to what I did. If > there's any possibility that it will emerge in, oh, a month or two, I > don't think it makes sense to go to the trouble to pull the HSRE code > into Apache. > >> >> If we have another implementation that works fine and has a sufficiently >> large enough community then I do not see a problem to include it in the >> commons project, I would certainly be interested. >> >> Thomas >> >>> On Mon, Feb 2, 2015 at 6:21 PM, Thomas Neidhart >>> wrote: >>>> On 02/02/2015 11:20 PM, James Ring wrote: >>>>> I spoke to one of the authors of re2j, a Google-internal port of the C++ >>>>> re2 library. The intention was to open source it but they just haven't got >>>>> around to it. >>>>> >>>>> I may try and get Google to put re2j up on GitHub so you all can take a >>>>> look. AFAIK it is heavily used in Google and it has an API that is largely >>>>> compatible with java.util.regex. I know from personal experience that one >>>>> can often benefit from re2j merely by replacing java.util.regex imports >>>>> with the corresponding re2j imports. >>>> >>>> that would be super-cool. >>>> >>>> Thomas >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>>> For additional commands, e-mail: dev-help@commons.apache.org >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>> For additional commands, e-mail: dev-help@commons.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org