Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41413
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.92.24 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=UsRrDtN/Xsn8BKz160El4f7t6py8V6NUl6pknxalhNB2iSJv9C0KdaN0UeBRLqL6+Q
         cmylRQYQ9OP1r+NwSoOZ6Isb+3delrQkUXMmOJ3MMkefdG7iSJGSHb3c9ObuQfGPWi9D
         5+x7M6bCkC1KgV5547JZgxZ/krvuPvmpDlXts=
Message-ID: <bcb7aa500810262116q52a4d703naf94864b89772662@mail.gmail.com>
Date: Mon, 27 Oct 2008 02:16:35 -0200
To: "Greg Beaver" <greg@chiaraquartet.net>
Cc: "Stan Vassilev | FM" <sv_forums@fmethod.com>, 
	"PHP internals" <internals@lists.php.net>
In-Reply-To: <49048CCB.2090407@chiaraquartet.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46BD96DF-B594-490C-9812-D7ACDD976205@pooteeweet.org>
	 <9373E34A42AC4CE0A65E512A61897512@pc>
	 <49048CCB.2090407@chiaraquartet.net>
Subject: Re: [PHP-DEV] </endnamespacediscussion>
From: guilhermeblanco@gmail.com ("Guilherme Blanco")

Hi guys,


I'm really interested to read the IRC conversation logs.
Does anyone recorded it?


Regards,

On Sun, Oct 26, 2008 at 1:29 PM, Greg Beaver <greg@chiaraquartet.net> wrote:
> Stan Vassilev | FM wrote:
>>
>> Hi,
>>
>> I want to thank you all for opting for the technically sound, clear and
>> performant solution. Of course some users will never understand the
>> precise reasons :: was avoided, but it's something we'll have to live
>> with, given some past design choices in PHP.
>>
>> Regarding "foo\tbar" turning into "foo[tab]bar", I just wanted to throw
>> it out there, although I don't think it's a great idea. We have only few
>> escape combinations in string literals which can also be in a valid
>> identifier:
>>
>> \t  \n  \r
>>
>> There are also some which aren't a problem since they can't be in a
>> valid identifier:
>>
>> \x..  \0  \\  \$  \'  \"  \{..} etc.
>>
>> So the problem is with exactly three combos:  \t, \n and \r. In the few
>> places PHP takes class/function identifiers as strings, TAB, CR and LF
>> could be interpolated back into the two characters they express, since
>> TAB, CR and LF aren't valid on their own in identifiers, so ambiguity is
>> not possible.
>
> there are other escape sequences (such as \f)
>
>> Those places of the top of my mind are:  new $class(), $class::property,
>> call_user_*(), _autoload, and all other places accepting callbacks.
>>
>> This would mean both of those will work correctly:  "foo\\tbar" and
>> "foo\tbar" when used as an identifier.
>>
>> Think of it as a plan B in case people cause a big fuss about it (which
>> I think they won't: think about escaping of windows file paths and
>> escaping in regex pattern, we're doing just fine there).
>
> I don't see this as a real problem, simply because when one makes a
> mistake, it is obvious.  A fatal error is displayed with the offending
> class name/function name/constant name (yes, namespace constants die
> with fatal error if they are not found, unlike traditional un-namespaced
> constants).  Although it may be possible to magically replace escaped
> characters, this could have unintended side effects.  For instance, if a
> user is instantiating a class based on external input, it would
> introduce a new way to have unexpected behavior, as newlines would be
> converted to \n or \r.
>
> As I stated in my last message on the subject, the best approach for any
> string is to always use single quotes.  You're far less likely to run
> into trouble.  This has been true for years, and is not changed by
> namespaces or any other addition in 5.3
>
> Shall we let this one go?
>
> Greg
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



-- 
Guilherme Blanco - Web Developer
CBC - Certified Bindows Consultant
Cell Phone: +55 (16) 9166-6902
MSN: guilhermeblanco@hotmail.com
URL: http://blog.bisna.com
Rio de Janeiro - RJ/Brazil