ID:               46326
 Updated by:       paj...@php.net
 Reported By:      RQuadling at GMail dot com
 Status:           Open
 Bug Type:         PHP options/info functions
 Operating System: win32 only
 PHP Version:      5.3CVS-2008-10-17 (snap)
 Assigned To:      pajoye
 New Comment:

New ini parser, not windows specific then, unassigned. 


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

[2008-12-19 11:17:47] rquadl...@php.net

Ah. This must be a change in PHP5.3, as the BOM is present on the ini 
file and is working with no problems on PHP5.2

So, this isn't a bogus report.




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

[2008-12-19 11:16:22] rquadl...@php.net

Unicode BOM on the INI file makes the INI file unreadable by php.exe 
with regard to INI settings, though can be read using 
file_get_contents(), etc.

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

[2008-12-19 11:15:29] RQuadling at GMail dot com

Oh bugger.

Went to a brand new out of the box system. Copied the latest PHP 
5.3.0alpha4-dev (cli) (built: Dec 19 2008 10:05:54).

Copied my error_reporting.ini file ...

error_reporting=E_ALL

Ran php -c error_reporting.ini -i | find "error_reporting" and got no 
values.

Did a type error_reporting.ini and then I slumped.

My editor is saving the BOM.

Removed the BOM and voi bloody la.

For the life of me, I can't get the BOM to NOT be saved in all 
instances.

So, making this a Bogus report and a getting the wall ready for some 
head banging.

Sorry for the noise.

I'll shutup now.

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

[2008-12-19 10:45:38] paj...@php.net

Using php.ini:
error_reporting = E_ALL

5.3.0-latest VC6:

C:\Users\pierre\Documents\test\php53vc6>php.exe -c php.ini  -i | find
"error_reporting"
error_reporting => 30719 => 30719

5.3.0-latest NTS VC9:
C:\Users\pierre\Documents\test\php53a2ntsvc9>php.exe -c php.ini  -i |
find "error_reporting"
error_reporting => 30719 => 30719

Tested on xp, vista, 2k3 and 2k8 (x86 and x64). It works as well inside
apache2 sapi or fcgi (iis7).

Not sure what's wrong on your system. Do you have a clean system
(without registry changes, no ini every where, etc.) to test again?

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

[2008-12-12 20:12:40] RQuadling at GMail dot com

Still having problems with this on Windows XP Pro SP3 and Windows 
Server 2005/2008.

php-5.3-win32-VC6-x86-latest >php -v
PHP 5.3.0alpha4-dev (cli) (built: Dec 12 2008 15:05:22)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2008 Zend Technologies

php-5.3-win32-VC6-x86-latest >php --ini
Configuration File (php.ini) Path: C:\WINDOWS
Loaded Configuration File:         C:\PHP\PHP5\INI\php-cli.ini
Scan for additional .ini files in: (none)
Additional .ini files parsed:      (none)

php-5.3-win32-VC6-x86-latest >type
C:\php\php5\ini\php-cli.ini | find "error_reporting"
error_reporting                 = E_ALL | E_STRICT

php-5.3-win32-VC6-x86-latest >php -i | find
"error_reporting"
error_reporting => no value => no value


Same results for ...

PHP 5.3.0alpha3 (cli) (built: Dec  4 2008 20:40:51)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2008 Zend Technologies


I even created a separate INI file ...

[PHP]
error_reporting = E_ALL | E_STRICT

and then ...

php-5.3.0alpha3-Win32-VC6-x86 >php -c
C:\php\php5\INI\error_reporting.ini -i | find "error_reporting"
Loaded Configuration File => C:\PHP\PHP5\INI\error_reporting.ini
error_reporting => no value => no value


I'm aware that Pierre is working around this area along with [PATH=] 
and [HOST=].

Posting this comment as another test case.

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

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

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

Reply via email to