I have to agree, this kind of change would be very frustrating for Win32
users, even though the solution is that simple.
Nobody reads update guides or installation instructions, they're used to
write path like that and they'll continue to do it, so we'll have much
more bug reports after the release if we keep it this way. Just try to
imagine how much PHP installations will suddenly stop working after the
upgrade.
I do agree that this syntax is actually correct and it should have been
done this way since the very beginning, but now it's too late for such
changes, we have to put the old behavior back.
I'm a Windows PHP user. It's never late for a change of that kind. Upgrading
your PHP installation is officially a Big Event, and tweakin the ini is a
one-time operation per upgrade, so I believe some people may be
overestimating the pain it will cause.
There won't be any bug reports, if the ini parser detects improper backslash
usage (i.e., using a backslash with a following character which doesn't form
correct escape combination) and stops with informative and descriptive
message explaining the parser changes. Then anyone who can read, will
figure it out, and fix it.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
