2 ms·
Look, 10 years ago I tried — really tried — to get the PHP team to adopt it. I am glad they finally came around: https://www.mail-archive.com/internals@lists.p
by EGreg 6y ago
Look, 10 years ago I tried — really tried — to get the PHP team to adopt it. I am glad they finally came around:
https://www.mail-archive.com/internals@lists.php.net/msg45871.html https://www.mail-archive.com/internals@lists.php.net/msg4587...
Excerpt of the proposal:
So why am I saying all of this? Well, PHP up until 4 had a reputation
for lots of bad coding style, spaghetti code, etc. With PHP 5 and
better OOP, this reputation has lessened, especially with the great
libraries out there (Zend Framework, Kohana, symfony, etc.) But there
is still a problem. We (or at least I) would want PHP 6's reputation
to be even better, and the reputation is largely based on how
maintainable and cost-effective the code is, which is written by
programmers actually using PHP. Blaming newbie programmers is one
thing, and may even have some truth to it (PHP is simple - thus
attracts newbies) but it's always good for a language to steer you in
the right direction by default, and make it easier to write
maintainable code.
PHP has a great opportunity to do this, by implementing a very simple
change, turning all current PHP 5 code, and all code that will be
written in the future, into maintainable code. Moreover, it won't
break any existing code, like some other additions to PHP 6 might do.
This one simple tweak will make PHP 6 code much more reusable and
maintainable, just like namespace support will potentially make future
PHP code more interoperable without having to write
Artificial_Namespace_Class, like ZF and PEAR do.
- Kim_Bruning 6y agoThank you for your efforts back then. And now you stand vindicated!
- EGreg 6y agoSomehow one guy was really sure it will never happen: https://www.mail-archive.com/internals@lists.php.net/msg48044.html https://www.mail-archive.com/internals@lists.php.net/msg4804...