----- Original Message -----
From: "George Schlossnagle" <[EMAIL PROTECTED]>
To: "Dean Hall" <[EMAIL PROTECTED]>
Cc: "Rasmus Lerdorf" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; "Andi Gutmans" <[EMAIL PROTECTED]>
Sent: Sunday, September 30, 2001 09.44pm
Subject: Re: [Zend Engine 2] Re: [PHP-DEV] Re: [Zend Engine 2] namespaces
ambiguity
> The point is that while those are both valid
>
> $test?FOO:BAR:BARBARA
>
> is ambiguous in that it could refer to either of those.
I guess my point is that I see no problem with a parse error message here
when it is ambiguous. To make it unambiguous, you would just use
curly-braces like this:
$test?FOO:{BAR:BARBARA}
(This seems like it would need some additional functionality in the parsing
engine to extend the curly-brace mechanism outside of
double-quotes/heredocs -- and to constants, not just variables.)
Also, I think that namespaces should allow no spaces between namespace names
and other namespace names or variable/class/constant names. e.g.:
FOO : BAR : BARBARA
is illegal as a fully-qualified constant name, so the following would
eliminate ambiguity as well:
$test ? FOO : BAR:BARBARA;
Dean.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
