Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12061
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20040810141045.46734.qmail@pb1.pair.com>
To: internals@lists.php.net
Reply-To: jay@php.net
Mail-Copies-To: jay@php.net
Date: Tue, 10 Aug 2004 10:10:12 -0400
References: <20040809205146.68684.qmail@pb1.pair.com> <200408091727.43956.ilia@prohost.org>
Lines: 22
User-Agent: KNode/0.7.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Subject: Re: [PHP-DEV] new browscap INI parser...
From: jay@php.net (Jay Smith)

Ilia Alshanetsky wrote:

> While anything would be better then the current solution I wonder is
> perhaps going the INI way is not the best idea due to the potential
> confusion. The fellow who supplies the ini files with browser information
> also has a csv file with the very same data that is much easier to parse.
> 
> Ilia
> 

I would think that sticking with the current ini files would probably lead
to less confusion. Just from the perspective that there may be people using
customized ini files or even just to avoid the initial "why is browscap
broken, my ini file is in the right place" bug reports and such. I wouldn't
expect any sort of register_globals-level "wtf", but it would probably be
enough to be annoying...

This modified parser isn't all that complicated anyways. The grammar and
lexer are both pretty small now, with the extraneous parsing normally done
on PHP's own ini file stripped out.

J