Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40275
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.233 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=eSLD8tr/YD50LuRb/Z8VcUNfV/jVJ7VZVTC5x6BkwDMA+CMLGuvHrpYTUcJNBsMTJQ
         ENCKbU8wKH98MM+HPORWSD+dc/QjQicABlJPVDi4l+fOrGBHd9GA8dtT3Gyb1ju0gs0g
         Rd8N+GfpeAeDRv9iP2OxeBqtliaVl77lzfTDM=
Message-ID: <fe05d1540809041424p580de876ub7d644d88adb53c0@mail.gmail.com>
Date: Thu, 4 Sep 2008 23:24:01 +0200
To: "Stanislav Malyshev" <stas@zend.com>
Cc: jani.taskinen@iki.fi, 
	"=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>, 
	"PHP Internals List" <internals@lists.php.net>, 
	"Pierre-Alain Joye" <pajoye@php.net>
In-Reply-To: <48C04E6A.2080909@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080904190717.aaz97tz688oogc4c@horde.chinstrap.eu>
	 <48C0488C.9090209@sci.fi> <48C04E6A.2080909@zend.com>
Subject: Re: [PHP-DEV] Re: ini-parsing, double quotes, windows in 5.3
From: pierre.php@gmail.com ("Pierre Joye")

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