Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28569
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cschneid.com from 195.226.6.51 cause and error)
Message-ID: <46039E2C.2020304@cschneid.com>
Date: Fri, 23 Mar 2007 10:30:20 +0100
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Tomas Kuliavas <tokul@users.sourceforge.net>
CC: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] String BC break \{$a}
From: cschneid@cschneid.com (Christian Schneider)

Tomas Kuliavas wrote:
> It was changed in 5.1.0-5.1.1 versions.
> 
> According to PHP Manual (http://www.php.net/language.types.string) curly
> brackets are not escaped with backslash. Escape worked in older PHP
> versions. It does not work in 5.1.1+.
> 
> http://bugs.php.net/31341
> http://bugs.php.net/35411

These two (fixed and closed) bugs diff from mine I think:
31341: $     \{	=> $     \{
vs.
35411: \{$string}	=> {$string}
vs.
my problem with PHP 5.1.5/5.2.1: \${string}	=> \{abc}
vs.
PHP4: \{$string}	=> {abc}

So with PHP 5.1.5 and PHP 5.2.1 curly braces *are* escaped (they are 
still output) but the backslash is output as well. If they would not be 
escaped at all I would have expected \abc. I still think the PHP4 way 
has the lowest WTF factor.

Is this behaviour an oversight (and I should open a bug report) or is 
this intentional? I'm still not sure.

- Chris