Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:8278
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20040301153521.16934.qmail@pb1.pair.com>
To: internals@lists.php.net
Reply-To: jay@php.net
Mail-Copies-To: jay@php.net
Date: Mon, 01 Mar 2004 10:35:20 -0500
References: <20040226215914.13204.qmail@pb1.pair.com> <Pine.WNT.4.56.0402292149080.3964@DELL>
Lines: 27
User-Agent: KNode/0.7.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Subject: Re: [PHP-DEV] Fix for #27291 (get_browser() problems)
From: jay@php.net (Jay Smith)

Rasmus Lerdorf wrote:

> Hey Jay, sorry, didn't notice this message until after sending out my
> previous request.  How do you feel about taking over maintaining the
> browscap code and splitting it off into its own pecl extension so you are
> not restricted by PHP's release schedule?
> 
> -Rasmus
> 

Splitting it off into PECL would probably be the best thing to do,
especially with PHP 5 looming on the horizon. Gary is somewhat concerned
that after 5 comes out, the problems that exist in the 4_3 branch will
continue to plague him and 4.3.x browscap.ini users, so splitting it off
from the PHP release sounds pretty logical. 

I'll volunteer to continue working on it, although hopefully most or all of
the issues concerning the pattern matching should be fixed by my patch. The
parser issues are another matter, but splitting it off into PECL will let
us fix that up without having to worry about a complete 4.3.x release.

So I'm +1 for this. The question is, do we split it off before the impending
4.3.5 release or afterwards? I would imagine that it should be done before.
If 4.3.5 goes out the door, browscap will be compiled in statically, so
that makes having it in PECL harder. 

J