#15975 [Com]: Parse error for lates version of browscap.ini

ID: 15975 Comment by: adf@sorcerer.co.uk Reported By: martijn@hooimeijer-it.com Status: Bogus Bug Type: PHP options/info functions Operating System: Windows 2000 PHP Version: 4.1.1 New Comment: Sorry, previous comment should have read "windows binary distribution", don't know about other distributions. At least I see you have finally accepted this as a bug in the 4.2.3 distribution and have apparently fixed it in CVS (Bug #19902) Previous Comments: ------------------------------------------------------------------------ [2002-11-16 13:19:31] adf@sorcerer.co.uk Sorry iliaa@php.net but this is a bug either in PHP or in browscap.ini and is not bogus at all! The **STANDARD** 4.2.3 windows distribution of PHP (.zip) includes this bug. The is *NOT* a support request. ------------------------------------------------------------------------ [2002-08-14 21:20:13] iliaa@php.net Sorry, but the bug system is not the appropriate forum for asking support questions. Your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Thank you for your interest in PHP. PHP does not support ! | ( ) characters as potential values, to prevent this problem remove those characters from the values of the entries inside your browscap.ini file. ------------------------------------------------------------------------ [2002-03-09 16:56:30] martijn@hooimeijer-it.com While reading the lates version of browscap.ini (version february 2002) the parser stumbles over brackets. E.g. an entry like: platform=Windows XP (Q312461) will trigger the error: PHP: Error parsing e:\PHP\browscap.ini on line 1397 When removing the brackets, e.g. platform=Windows XP Q312461 the parser does not stumble. Brackets appear on about 10-20 lines in the browscap.ini. It is a drag to remove all the brackets for each and every update of the file. Fix seems to be relatively quick, with a great benefit. This bug may have a similar cause as bug #10060. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=15975&edit=1