Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:8264 php.pecl.dev:445 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85559 invoked by uid 1010); 1 Mar 2004 08:17:09 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 85511 invoked from network); 1 Mar 2004 08:17:09 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 1 Mar 2004 08:17:09 -0000 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id i218Gt9b016713; Mon, 1 Mar 2004 09:16:55 +0100 Date: Mon, 1 Mar 2004 09:16:54 +0100 (CET) X-X-Sender: derick@localhost To: Rasmus Lerdorf cc: internals@lists.php.net, pecl-dev@lists.php.net In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Cleaning up the browscap mess From: derick@php.net (Derick Rethans) On Sun, 29 Feb 2004, Rasmus Lerdorf wrote: > I would suggest as a first step to pull it out of ext/standard and create > a pecl extension for it and second to go through and figure out if we can > continue to use the ini parser for this, which I am guessing we can't, so > the third task is likely to write a new parser for it. If you make it a pecl extension it won't be available to a lot of people, so I think it's not a good idea to do so. Derick