Doc #44575 [Com]: parse_ini_file comment # line problems

Edit report at http://bugs.php.net/bug.php?id=44575&edit=1 ID: 44575 Comment by: jihoy at admin dot com Reported by: letssurf at gmail dot com Summary: parse_ini_file comment # line problems Status: Closed Type: Documentation Problem Package: Documentation problem Operating System: * PHP Version: 5.3CVS-2008-11-01 Block user comment: N Private report: N New Comment: Wow...the php is really great, thank you very much for sharing it!! http://www.amerisleep.com Previous Comments: ------------------------------------------------------------------------ [2009-08-07 14:59:04] jani@php.net This is duplicate report of bug #47703 which now includes some explanations too. :) ------------------------------------------------------------------------ [2008-11-02 23:39:03] lbarnaud@php.net 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. open -> to be documented. Comments starting with # has been re-enabled in 5.3, but they throw an E_DEPRECATED warning. ------------------------------------------------------------------------ [2008-11-02 14:04:33] jani@php.net This really should be solved before PHP 5.3.0 goes out. Might otherwise cause pretty hard to find secondary "bugs". ------------------------------------------------------------------------ [2008-10-17 11:40:00] konstantin at symbi dot org the behaviour which stops parsing on '#' breaks compatibility with php 5.2. at least it should be documented, and an error/warning raised, but i do not understand the reason of breaking BC. ------------------------------------------------------------------------ [2008-04-02 10:28:31] jani@php.net Yes, that's why I didn't bogus this. Propably we could allow # as comment too, but I'd still reserve it for #if..#else..#endif style constructs. Marcus, what's the deal with that? ------------------------------------------------------------------------ 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/bug.php?id=44575 -- Edit this bug report at http://bugs.php.net/bug.php?id=44575&edit=1