Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:14524
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20050202153138.15001.qmail@lists.php.net>
To: internals@lists.php.net
Reply-To: jay@php.net
Mail-Copies-To: jay@php.net
Date: Wed, 02 Feb 2005 10:31:37 -0500
References: <5.1.0.14.2.20050201111730.0299da70@localhost> <20050202005157.83298.qmail@lists.php.net> <4200449D.3000904@prohost.org>
Lines: 26
User-Agent: KNode/0.8.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Subject: Re: [PHP-DEV] Re: PHP 5.1
From: jay@php.net (Jay Smith)

Ilia Alshanetsky wrote:

> Jay,
> 
> I've noticed that you're still using the ini parser in this new code,
> would it not be easier and allow for greater code re-use to use the CSV
> database and the underlying fgetcsv code?
> 
> Ilia
> 

Hi Ilia, long time no irc...

It probably would be a lot easier to go with the CSV parser as far as code
maintenance is concerned, but I think the wtf factor may make it more
annoying than it's worth. I can already picture bug reports saying "my
browscap.ini file isn't being read any more, what gives". I'm sure it would
be no where close to as bad as register_globals, but still, it's some
unnecessary BC breakage that will probably be more trouble than it's worth.

This is a x.1 release, so I guess this would be the time to do a semi-major
change like this, but I personally don't think it's warranted from the
users perspective. Just an unnecessary (albeit quite minor) hurdle to
upgrading to 5.1, imho.

J