Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40277
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain macvicar.net from 193.227.246.108 cause and error)
References: <20080904190717.aaz97tz688oogc4c@horde.chinstrap.eu> <48C0488C.9090209@sci.fi> <48C04E6A.2080909@zend.com> <fe05d1540809041424p580de876ub7d644d88adb53c0@mail.gmail.com>
Message-ID: <BE082EF6-ABE0-47A2-B494-97E40BE3D90B@macvicar.net>
To: Pierre Joye <pierre.php@gmail.com>
In-Reply-To: <fe05d1540809041424p580de876ub7d644d88adb53c0@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 5C1)
Date: Thu, 4 Sep 2008 23:10:16 +0100
Cc: Stanislav Malyshev <stas@zend.com>,
 "jani.taskinen@iki.fi" <jani.taskinen@iki.fi>,
 =?utf-8?Q?Johannes_Schl=C3=BCter?= <johannes@php.net>,
 PHP Internals List <internals@lists.php.net>,
 Pierre-Alain Joye <pajoye@php.net>
X-Spam_Report: Spam detection software, running on the system "lovelace.midden.org.uk", has
	identified this incoming email as possible spam.  The original message
	has been attached to this so you can view it (if it isn't spam) or label
	similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview:  I agree, users will notice quickly enough and the previous
	behaviour doesn't match that of PHP. If we provide an uprade information
	popup at the end of the Windows installer it might help. Scott [...] 
	Content analysis details:   (-2.5 points, 5.0 required)
	pts rule name              description
	---- ---------------------- --------------------------------------------------
	-1.8 ALL_TRUSTED            Passed through trusted hosts only via SMTP
	1.9 TVD_RCVD_IP            TVD_RCVD_IP
	-2.6 BAYES_00               BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
Subject: Re: [PHP-DEV] Re: ini-parsing, double quotes, windows in 5.3
From: scott@macvicar.net (Scott MacVicar)

I agree, users will notice quickly enough and the previous behaviour  
doesn't match that of PHP.

If we provide an uprade information popup at the end of the Windows  
installer it might help.

Scott

On 4 Sep 2008, at 22:24, "Pierre Joye" <pierre.php@gmail.com> wrote:

> hi,
>
> On Thu, Sep 4, 2008 at 11:08 PM, Stanislav Malyshev <stas@zend.com>  
> wrote:
>> Hi!
>>
>> I don't think something allowed and documented can be just remove  
>> without
>> considering the consequences. It worked and did what it was  
>> intended to do,
>> why we need to drop it?
>> If people actually have configs that would stop working in 5.3 and it
>> wouldn't be good for anybody. In windows, because of spaces, a lot  
>> of people
>> would have include_path with quotes, and also most of them use \,  
>> because
>> they just copy-paste these paths.
>> I'm also not sure how you'd have these people fix it. Say you have  
>> path
>> like: "c:\Documents and Settings\John Doe\My Documents\PHP Projects 
>> \Cool
>> Site Project\include\" - you'd have everybody to manually scan each  
>> such
>> string and replace \ with /? Or just drop final \?
>
> Or simply remove the double quotes.
>
> include_path=C:\Users\pierre\Documents\Digsby Logs
>
> works just fine.
>
> I think we are making a big problem of a non issue. This issue is easy
> to catch and fix. If a problem occurs in an app, it will be visible
> very quickly, like for missing extensions or wrong include_path.
>
> Cheers,
> -- 
> Pierre
> http://blog.thepimp.net | http://www.libgd.org
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>