AW: [STANDARDS] Use declaration outside of namespace
[email protected] ("Robert Stoll")
| Newsgroups | php.standards |
|---|---|
| Message-ID | <[email protected]> |
> -----Ursprüngliche Nachricht----- > Von: Robert Stoll [mailto:[email protected]] > Gesendet: Mittwoch, 29. Oktober 2014 20:42 > An: 'Stas Malyshev'; [email protected] > Betreff: AW: [STANDARDS] Use declaration outside of namespace > > > -----Ursprüngliche Nachricht----- > > Von: Stas Malyshev [mailto:[email protected]] > > Gesendet: Mittwoch, 29. Oktober 2014 19:03 > > An: Robert Stoll; [email protected] > > Betreff: Re: [STANDARDS] Use declaration outside of namespace > > > > Hi! > > > > > I always found it very ugly that it is possible to define a use > > > outside of a namespace. Consider the following: > > > > This is not a question of standardization, which is meant to discuss > > what is currently happening in the language, not changes to it. So it should be discussed on internals. > > > > I disagree, the standardization process should not merely cover one-to-one what happens in PHP 5.6 because the > specification shall be the basis for other PHP implementations and therefore such "features" as the one I mentioned > should not be part of the spec -- or would you claim that other implementations have to include this "feature" as well? > As I mentioned in the first email, the fact that PHP has implemented this "feature" is not a bug. As long as an > implementation is just a superset of the spec it is fine IMO. Such an implementation is still able to parse and execute PHP as > mentioned in the spec. > But sure, if no one wants to discuss this here I can drop an email to internals. Yet, as I argued, I think it is the right place. > I was a little bit too quick. You are actually right, another implementation needs to implement this feature as well otherwise it could not execute a PHP script which actually uses this "feature". I'll drop an email @internals