On 11/26/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: > The only thing that matters is whether i can write a correct > lexer/parser for this without breaking stuff.
Im no parser expert at all, so just to be sure that I understand the problem correctly: I guess you can't distinguish at the parser/lexer level between cases where it's ambiguos without white spaces and where it isn't? Alternatively, could you provide a configuration switch to turn the use of namespace constants in the ternary on or off? (So that people who don't use namespace constants but use the ternary without spaces wouldn't need to change all their code?) Personally, as a PHP user, I'd strongly prefer the double colon to the backslash because it's much more self-explaining and nicer. But on the other hand, if there is really no solution for the double colon, anything that gives us namespace support at all is greatly appreciated. Better have namespaces with backslash than not have them at all. Regards, Sebastian -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
