Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40261
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 81.169.179.180 as permitted sender)
Message-ID: <20080904190717.aaz97tz688oogc4c@horde.chinstrap.eu>
Date: Thu, 04 Sep 2008 19:07:17 +0200
To: PHP Internals List <internals@lists.php.net>
Cc: Pierre-Alain Joye <pajoye@php.net>, "jani.taskinen"
	<jani.taskinen@iki.fi>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
Subject: ini-parsing, double quotes, windows in 5.3
From: johannes@php.net (Johannes =?iso-8859-1?b?U2NobPx0ZXI=?=)

Hi,

now that we have a publicly available alpha on Windows we get the first
feedback from Windows users. Within quite short time we got two bug
reports (#45992 #45994) about a change in the ini-parsing:

With <=5.2 we allow

   include_path = "c:\foo\bar\"

and treat the backslash as regular character. It's documented that way
in http://de.php.net/manual/en/configuration.php example #1 and in
php.ini-recommended.

This was caused by the changes in the ini parser which are important,
but in my opinion this is a break where we should try to find a way to
keep the behavior, especially as it was in the "recommended" php.ini
file and other places before.

Pierre completely disagrees, I guess he'll answer to this mail and tell
why :-)

Opinions from others, a good proposal to keep the improved ini handling
and making this work? :-)

johannes


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.