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 \?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
