Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33411
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain simps.ru designates 87.245.154.216 as permitted sender)
Date: Sat, 24 Nov 2007 12:33:31 +0600
Reply-To: Dagdamor <dagdamor@simps.ru>
Message-ID: <11310531742.20071124123331@simps.ru>
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [PHP-DEV] Re: 5.2.5 - changes in the string parser
From: dagdamor@simps.ru (Dagdamor)

>> The documentation probably should be fixed. Also, \f and \v have been
>> documented; your mirror probably isn't up to date. See:
>> http://cvs.php.net/viewvc.cgi/phpdoc/en/language/types.xml?r1=1.189&r2=1.190&diff_format=u

This is the mirror I'm using - http://www.php.net/manual/en/language.types.string.php
Dunno if it's up to date or not. IMO, if you stated in the past that only
certain characters are being escaped *while others are not*, you shouldn't
change this in the future (even by making changes in the documentation),
because it breaks existing code.

Moreover, you still can't use "\f" or "\v" sequences in your code, even if you
want them to generate FF and VT symbols. Even PHP 5.2.4 treats them in a
different way, leaving alone older versions of PHP. If you want to write code
that will be compatible with different versions (which is important nowadays),
you can't use these sequences at all. And again, why adding them in the first
place? Who needs FF or VT on a regular basis in their applications?

Regards,
Serge