Re: Re: ini-parsing, double quotes, windows in 5.3

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