Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40262
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.170 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=NpDtU/KrjyhXlRH/26gCw1JgEuZSWtAncL8pv0Jv/Os5DPtgfZESmzUQa+JIDGB3Lp
         QVVruf5ZEoxzfSiyxFBXGDuCD2c5eNnp7lUllDeq6YSv9NvLQwYOTmfGdxmujVy4Fysu
         u2GTUeGo5UG+m0fhAyKF2xkAPA00mvpP2JbiA=
Message-ID: <fe05d1540809041015r4ceac434jeddd062471ea8581@mail.gmail.com>
Date: Thu, 4 Sep 2008 19:15:23 +0200
To: "=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>
Cc: "PHP Internals List" <internals@lists.php.net>, 
	"Pierre-Alain Joye" <pajoye@php.net>, 
	jani.taskinen <jani.taskinen@iki.fi>
In-Reply-To: <20080904190717.aaz97tz688oogc4c@horde.chinstrap.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20080904190717.aaz97tz688oogc4c@horde.chinstrap.eu>
Subject: Re: [PHP-DEV] ini-parsing, double quotes, windows in 5.3
From: pierre.php@gmail.com ("Pierre Joye")

hi,

On Thu, Sep 4, 2008 at 7:07 PM, Johannes Schl=FCter <johannes@php.net> wrot=
e:
> 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 <=3D5.2 we allow
>
>  include_path =3D "c:\foo\bar\"

> Pierre completely disagrees, I guess he'll answer to this mail and tell
> why :-)

Things is that we have expandable variables now (or env). I think that
having double quotes working like in php is a good and safe thing. It
could be too tricky (or pointless) to have to deal with two kind of
backslashes, depending on the context. Especially as (and Johannes
should have mentioned it in his mail) the fix is as easy than:

include_path=3Dc:\foo\bar\

or

include_path=3D"c:/foo/bar/"

Cheers,
--=20
Pierre

http://blog.thepimp.net | http://www.libgd.org