Re: Re: PHP 5.1 (Or How to break tousands of apps out there)
| From: | Jessie Hernandez | Date: | Sat, 26 Nov 2005 06:00:06 +0000 |
| Subject: | Re: Re: PHP 5.1 (Or How to break tousands of apps out there) | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-20494@lists.php.net to get a copy of this message | ||
Bob Silva wrote:
Like I said before, I personally don't care for namespace constants, so if this whitespace/parentheses "limitation" is unacceptable, then I can simply remove namespace constants support from my patch. I would like to hear more opinions on this, though, before I take any further action. Regards, Jessie P.S. It would be really good to have some sort of polling feature on php.net where we can post polls, so we can get users' feedback on things before making changes (as opposed to just asking the subscribers of the internals list).$x = $y ? foo:bar:baz:stupid;I think "stupid" is the key word here, by forcing the whitespace or (), you are making the language itself stupid by not knowing how to parse itself. I'm not a core developer, but I am pretty sure that this implementation will never be accepted, so change your argument to something more agreeable (like no namespace constants) and it may have a better chance of acceptance or the alternative is to have \ the accepted delimeter for namespaces which we both agree is not the best solution. I don't think having namespace constants is reason enough for such an awkward syntax. Any core functionality that uses globals now that is moved to an object will require code modifications anyways, so I don't think that’s a valid argument for the need of namespace constants. Bob Silva