#44575 [Tbd->Csd]: parse_ini_file comment # line problems

From: Date: Fri, 07 Aug 2009 14:59:05 +0000
Subject: #44575 [Tbd->Csd]: parse_ini_file comment # line problems
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-2619@lists.php.net to get a copy of this message
 ID:               44575
 Updated by:       jani@php.net
 Reported By:      letssurf at gmail dot com
-Status:           To be documented
+Status:           Closed
 Bug Type:         Documentation problem
 Operating System: *
 PHP Version:      5.3CVS-2008-11-01
 New Comment:

This is duplicate report of bug #47703 which now includes some
explanations too. :)


Previous Comments:
------------------------------------------------------------------------

[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?

------------------------------------------------------------------------

[2008-04-02 09:44:51] letssurf at gmail dot com

true.

Shouldn't the function either report a parse error or using them as
comments.

------------------------------------------------------------------------

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/44575

-- 
Edit this bug report at http://bugs.php.net/?id=44575&edit=1



Thread (4 messages)

« previous php.doc.bugs (#2619) next »