|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2018-10-03 09:34 UTC] [email protected]
-Status: Open
+Status: Verified
[2018-10-03 09:34 UTC] [email protected]
[2018-10-03 11:15 UTC] [email protected]
-Summary: parse_ini_file, parse_ini_string INI_SCANNER_RAW and
inline comments
+Summary: INI_SCANNER_RAW doesn't strip trailing whitespace
[2018-10-03 11:15 UTC] [email protected]
[2018-10-08 13:39 UTC] [email protected]
[2018-10-09 05:29 UTC] [email protected]
[2018-10-09 05:29 UTC] [email protected]
-Status: Verified
+Status: Closed
[2018-10-09 05:29 UTC] [email protected]
[2018-10-09 05:29 UTC] [email protected]
[2018-10-09 05:29 UTC] [email protected]
|
|||||||||||||||||||||||||||
Copyright © 2001-2026 The PHP GroupAll rights reserved. |
Last updated: Tue Mar 17 11:00:01 2026 UTC |
Description: ------------ When a line contains a comment after the value, parse_ini_string and parse_ini_file in INI_SCANNER_RAW mode pass double quotes and optionally spaces into the value, but strip the semicolon and comment. Logically, if inline comments (comments not taking the whole line) are supported, they should be stripped before parsing the values. If such comments are not supported, they should be included into the value. If this is normal and expected behaviour, it should be documented. Test script: --------------- <?php $ini = <<<END [section] 1="Hello" 2="Hello" ; comment END; var_dump(parse_ini_string($ini,true,INI_SCANNER_RAW)); $tmp = tempnam('.','tmp'); file_put_contents($tmp,$ini); var_dump(parse_ini_file($tmp,true,INI_SCANNER_RAW)); unlink($tmp); Expected result: ---------------- Expecting either to elements 1 and 2 with the same value, or element 2 containing the inline comment if inline comments are not supported. Actual result: -------------- array(1) { ["section"]=> array(2) { [1]=> string(5) "Hello" [2]=> string(8) ""Hello" " } }