#46347 [Asn->Csd]: parse_ini_file() does not like asterisk (*) in key
ID: 46347
Updated by: nlopess@php.net
Reported By: duke at masendav dot com
-Status: Assigned
+Status: Closed
Bug Type: Scripting Engine problem
Operating System: *
PHP Version: 5.3CVS-2008-11-11
Assigned To: scottmac
New Comment:
This bug has been fixed in CVS.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2009-01-01 23:10:10] nlopess@php.net
jani: try [*] or "*" to match a single '*' char
------------------------------------------------------------------------
[2009-01-01 11:57:00] jani@php.net
I don't know how to allow literal * in re2c. (\* did not work)
And I don't have spare time to debug this. Ask Pierre if he has.
------------------------------------------------------------------------
[2008-12-24 13:58:39] scottmac@php.net
Jani, this wasn't broken by any of the re2c stuff.
The changes you made to zend_ini_scanner.l revision 1.48 are the cause.
------------------------------------------------------------------------
[2008-10-20 21:01:03] duke at masendav dot com
More like undocumented feature then. Nothing at
http://www.php.net/parse_ini_file says that * cannot
be used inside
keys. So we are using it in a few in-house applications and this came as
unpleasant surprise.
We can of course implement a different solution, if you really consider
the current (5.2) behaviour bug.
In which case it would be nice to have a better explanation in
parse_ini_file documentation with regard to what is considered a valid
syntax and what not.
------------------------------------------------------------------------
[2008-10-20 20:45:16] jani@php.net
Why should it like it? That looks like a bug that got fixed by the
new parser.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/46347
--
Edit this bug report at http://bugs.php.net/?id=46347&edit=1
Thread (9 messages)