Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12045 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7837 invoked by uid 1010); 9 Aug 2004 21:28:08 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 4977 invoked from network); 9 Aug 2004 21:27:39 -0000 Received: from unknown (HELO asuka.prohost.org) (69.196.31.138) by pb1.pair.com with SMTP; 9 Aug 2004 21:27:39 -0000 Received: (qmail 4283 invoked from network); 9 Aug 2004 21:27:38 -0000 Received: from rei.nerv (HELO dummy.com) (rei@192.168.1.1) by asuka.nerv with SMTP; 9 Aug 2004 21:27:38 -0000 Reply-To: ilia@prohost.org To: jay@php.net, internals@lists.php.net Date: Mon, 9 Aug 2004 17:27:43 -0400 User-Agent: KMail/1.6.1 References: <20040809205146.68684.qmail@pb1.pair.com> In-Reply-To: <20040809205146.68684.qmail@pb1.pair.com> Organization: Prohost.org MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: <200408091727.43956.ilia@prohost.org> Subject: Re: [PHP-DEV] new browscap INI parser... From: ilia@prohost.org (Ilia Alshanetsky) 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 On August 9, 2004 04:51 pm, Jay Smith wrote: > Sort of a repost from last week, but it was probably just lost within the > torrent of goto posts... > > I finally got a bit of time away from work and whatnot to finally fix the > oddities with the browscap/ini parser. > > A tarball with the patch and the new files for HEAD is available at > > http://bugs.tutorbuddy.com/download.php/browscap.patch.tar.gz > > It's basically just a rip of some of the code from Zend/zend_ini_(parser > scanner).* with a few modifications to prevent operator handling and that > sort of thing. It still uses the Zend ini code for pretty everything except > the actual parser and scanner. > > I know this probably won't get into the 5.0.x branch, but I'd like to get > it into 5.1.0 if possible. I've only had a chance to test it out on linux, > so I have no idea if it builds on Windows or anything else for that matter > (my Win2k dev box was recently reappropriated at work so I can't test it at > the moment) so if somebody could take a look at that I'd appreciate it. I > have no idea how to manipulate the newer Windows builds, and have no Win32 > compiler at the moment anyways... > > If everything checks out, I'd like to commit it to HEAD sometime in the > near future... > > thx > > J