Re: [PHP] Best practices to ensure compatibility with PHP 6

Davi wrote: Em Domingo 22 Abril 2007 18:54, [EMAIL PROTECTED] escreveu: ... Have a look at PHP metting [1] and PHP-wiki [2]... =] [1] - http://www.php.net/~derick/meeting-notes.html [2] - http://oss.backendmedia.com/PhP60 Thank you for the links - it will get me started. -- PHP General

Re: [PHP] php seems to be inconsistent in its handling of backslashes ... maybe?

Richard Lynch wrote: ?php preg_match('#\\#','any-string'); = warning This seemed strange: warnings with 2 and 6 backlashes For 2 backslashes, PHP ate the 2 backslashes, and handed PCRE #\#, and PCRE does not like that at all. Yet preg_match('#\\#','any-string'); does *not* throw a

Re: [PHP] php seems to be inconsistent in its handling of backslashes ... maybe?

Al wrote: The proper way to handle special control PCRE characters like \ is to use the hex [e.g., \x5C] value. Then you won't have a problem. The engine knows you want the the object treated as a character and an a control. That works nicely, thank you. -- PHP General Mailing List

[PHP] Best practices to ensure compatibility with PHP 6

Hi I'm would like to avoid PHP usages that are deprecated with regard to PHP 6. I would also like to code according to what is regarded as best practice. Are there any web resources that I can read to keep up to date? For instance: 1) safe_mode is deprecated. (The PHP manual gives me the

[PHP] php seems to be inconsistent in its handling of backslashes ... maybe?

-- or maybe it's just the PCRE extension -- or quite likely I have got something wrong Hello members, I'm hoping you could enlighten me. Using error_reporting = E_ALL | E_STRICT, I tested the following statements: ?php preg_match('#\\#','any-string'); = warning