php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #43328 About the bugs #42590, #43316
Submitted: 2007-11-19 02:58 UTC Modified: 2007-11-19 13:18 UTC
From: dagdamor at simps dot ru Assigned:
Status: Not a bug Package: Strings related
PHP Version: 5.2.5 OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
48 - 11 = ?
Subscribe to this entry?

 
 [2007-11-19 02:58 UTC] dagdamor at simps dot ru
Description:
------------
To Ilia, http://bugs.php.net/bug.php?id=43316

Are you sure?

Check carefully the http://www.php.net/manual/en/language.types.string.php, table 11.1, and what's written right after it.

One should think a little bit before making fundamental changes in the parser and breaking BC *that* much... >:|


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-11-19 08:34 UTC] carsten_sttgt at gmx dot de
> Check carefully the table 11.1

I confirm with you, "\v" and "\f" are no valid escape sequences, according to the PHP manual. Thus a PHP programer must not take care about this escape sequences. Especially for existing scripts.


Just a additinal question:
PCRE nows the escape sequence "\f". Correct, you can read this in the PHP manual [1].

But what's about "\v"? Here I have this informations:
| Perl 5 no longer includes vertical tab in its set of whitespace
| characters.
| The \v escape that was in the Perl documentation for a long time
| was never in fact recognized.

Of course, on my system (PHP5.2.5/Win, PCRE compiled by PHP), a "\v" matches: "LF, VT, FF, CR"?

Regards,
Carsten

[1] http://de.php.net/manual/en/reference.pcre.pattern.syntax.php
 [2007-11-19 13:18 UTC] jani@php.net
Please don't open more reports about same issue. Use the magic "email" thing to either email directly to the person who bogused your earlier report or raise the issue on internals@lists.php.net. This is not a discussion forum.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Mar 29 14:01:28 2024 UTC