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 <bimargul...@gmail.com> wrote: > On Tue, Feb 3, 2015 at 2:39 AM, Thomas Neidhart > <thomas.neidh...@gmail.com> 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 >>> <thomas.neidh...@gmail.com> 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-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
