Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40502
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: "Arnaud Le Blanc" <arnaud.lb@gmail.com>,
 internals@lists.php.net
Message-ID: <44483922-2E93-4EE9-AA5C-5C22634CEACA@pooteeweet.org>
To: Pierre Joye <pierre.php@gmail.com>
In-Reply-To: <fe05d1540809121016k1d95bcb6nbb76bd729624a0b0@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Sat, 13 Sep 2008 11:30:17 +0200
References: <200809121821.15126.arnaud.lb@gmail.com> <fe05d1540809121016k1d95bcb6nbb76bd729624a0b0@mail.gmail.com>
Subject: Re: [PHP-DEV] Making ereg extension optional ?
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 12.09.2008, at 19:16, Pierre Joye wrote:

> hi,
>
> On Fri, Sep 12, 2008 at 6:21 PM, Arnaud Le Blanc  
> <arnaud.lb@gmail.com> wrote:
>> Hi,
>>
>> PHP now builds and works without ereg, is it planed to make it  
>> optional ?
>
> It is planed to drop it so I suppose optional can be a first step. I
> remember something about adding a BC layer using pcre, I'm not sure if
> it is done yet. However I would not do it in 5.x.


I think Andrei was pondering doing such a BC layer for PHP6, but I  
dont think this has been done yet. I think there were still  
discussions about if its feasible at all. This also means that there  
were discussions about if to even drop it, but I think we agreed on  
dropping it in the end, so I guess using ereg should throw an  
E_DEPRECATED in 5.3?

I am not sure if we should make it optional in 5.3 though.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org