Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76984 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93297 invoked from network); 31 Aug 2014 11:01:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Aug 2014 11:01:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.50 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.192.50 mail-qg0-f50.google.com Received: from [209.85.192.50] ([209.85.192.50:35063] helo=mail-qg0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/C0-22700-06003045 for ; Sun, 31 Aug 2014 07:00:58 -0400 Received: by mail-qg0-f50.google.com with SMTP id q108so4041161qgd.37 for ; Sun, 31 Aug 2014 04:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8w6PjWYDLahU8t/VoI2ybYXj7kKMlnZGd79gM+tOL9g=; b=y5XDqoj8W3cHJiBKAoZY4y26nRy79OPv2GN6302Sm1edYCeRuSxTWyvWO2RDz1/02e 7ooDjaB/kUQRxWSMObXUnAQN1w24vYJKL5HKvrBXR1+MeJnEr8rtELoDoBR0Qjdi8hVz 0xqXvFxYVGHKO48J0tEwHIJY7TAJeUXkEJJ4VqeqR1+H7jIjewQBQ540R4/XGPX/HNiO ei3Lq26YzWLGqeP7uTdg2trk9YxyzlDxDkjf3kOg1lLSXjxHXfJ6QsB7nZ7pZj3d2hDn PC2HzYYWeAZRt9KuVIHUR2eYCV5oiy7DczwGZqI35oP3gqrSwHSnybTr4GZfNx1CzlOy SRzw== MIME-Version: 1.0 X-Received: by 10.224.114.136 with SMTP id e8mr33845269qaq.67.1409482843182; Sun, 31 Aug 2014 04:00:43 -0700 (PDT) Received: by 10.140.80.210 with HTTP; Sun, 31 Aug 2014 04:00:43 -0700 (PDT) In-Reply-To: <137F7EB5-9A04-4780-A5F7-31089DEC959C@gmail.com> References: <137F7EB5-9A04-4780-A5F7-31089DEC959C@gmail.com> Date: Sun, 31 Aug 2014 13:00:43 +0200 Message-ID: To: Tjerk Meesters Cc: PHP Internals Content-Type: multipart/alternative; boundary=047d7bea3b742f5e9e0501eacc43 Subject: Re: [PHP-DEV] Kill ereg with fire From: tyra3l@gmail.com (Ferenc Kovacs) --047d7bea3b742f5e9e0501eacc43 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, Aug 31, 2014 at 7:08 AM, Tjerk Meesters wrote: > Hi internals (again), > > Recently I=E2=80=99ve done a small assessment on how feasible it is to re= move > ext/ereg from the project for the next major version. This is the result > (so far): > > https://github.com/datibbaw/php-src/compare/kill-ereg > > I=E2=80=99ve replaced two instances of ereg with their pcre equivalents, = OPcache > and PGSQL. > > Btw, simply using =E2=80=98pcreposix.h=E2=80=99 didn=E2=80=99t work out f= or OPcache, I would get > this error: > > Error Blacklist compilation: invalid argument to regex routine > > Perhaps I=E2=80=99ve missed something obvious, but porting it wasn=E2=80= =99t hard either. > > Thoughts? Afair we have a patch floating around, but never made it into the repo, but everybody seemed to agree to remove the core dependency of ereg and make it optional to enable. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --047d7bea3b742f5e9e0501eacc43--