Re: solving the namespace conflict issues between function/staticmethod class constant/ns constant
| From: | Jochem Maas | Date: | Tue, 23 Sep 2008 13:23:49 +0000 |
| Subject: | Re: solving the namespace conflict issues between function/staticmethod class constant/ns constant | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-40638@lists.php.net to get a copy of this message | ||
Lester Caine schreef:
Jochem Maas wrote:funnily enough yes.in the long run functions and constants will be added to namespaces ... and then the ambiguity issues will have to be dealt with. I believe Greg's namespace member concept will be required even if the syntax is/must/should/will changed to something everyone finds acceptable.Did you really mean to say that.
Push namespaces out now - incomplete - and then change them again later?it's not imcomplete anymore than autoload() is incomplete (autoload() also doesn't cater for functions). and it's not *change later* but *extend later* whereas if one would roll out the currently implementation with functions/constants you would have to *change it later* to fix the ambiguity issues (which is hard to do in a way that satisfies anyone, see reactions to Greg's namespace member proposal as a perfect example of the ammount of friction that one needs to overcome). changing it later implies that people will have to fix their code upon a new release of php at some point because they have been using namespaced functions/constants. if they can't use something then they don't have to change the code that doesn't use it either.
Why should we even bother using them if they don't do the whole job and are going to change again.not *changed* but *extended*. it seems obvious that BC dictates that stuff put out the door shouldn't be broken willy nilly. granted this will probably make it more difficult to come up with an alternative to Greg's proposal that also satisfies the ambiguities issues yet does not force syntax changes on developers using namespaces with released versions of php ... but that's not your f***ing problem is it? that'll be up to people like Stas, Greg, Dmitry et al to actually hammer out a solution.
Things like PHPEclipse and phpdocumentor need some major work to support this extra level, and that can't start until the format has been fixed - and now even that is not certain ?... same argument as above. I'll grant that my argument/opinion may be incorrect but I'll leave it up to the guys who build php to call me out on that.