Hi! > The current approach to namespaces blocks new features like you see it > in the following PR. The link already points to the two most relevant > comments that should give you full context: > > https://github.com/php/php-src/pull/947/#issuecomment-224912697
I don't think this - private classes, etc. - is a good idea. It looks like Javaization of the language and introducing more and more complexity without any clear benefit, and AFAIK none of the mainstream scripting languages have such concept. Anyway, this doesn't even have an RFC, so I don't see why we should refactor everything to accommodate it. But it is certainly does not fit the concept of namespaces. It needs completely different packages concept - one that currently does not exist on PHP. Trying to bolt it on existing concept is not going to do any good. I think this is what it should start with - developing a good concept, not trying to go from code modification to design. Design should come first, then code modification. > You might know other approaches to solve this. What I want to say is, we > should not re-discuss everything that was discussed before, we should > discuss the proposed features and refactor the namespaces IF it is required. Indeed. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
