Re: PHP Specification

Hello everyone! Took some time to read the discussion first before writing anything, so, here are some thoughts from the userland developer :) The idea of PHP Spec probably is floating around for a long time and for good reasons. As we approach the time, when PHP.next becomes a reality, it is a good time to do it. I also think it is a good idea to revise if some rarely used PHP features, that are not implemented in alternate implementations at all, are worth keeping. Sure, this will not go unnoticed, but pros and cons. Some of it is not implemented in alternate engines due to performance or is just not worth it. So, an evaluation is in order I believe. The second good thing that can come out of it is reevaluation of some type juggling, clearing up some edge cases and probably finally dealing with the type hints that generated so much heat and controversy on the list number of times. On that note, clearing up and tightening up other edge cases is a good thing. BUT! Before everyone gets on the wagon I want to remind everyone that although PHP Spec is a good thing, there are other more important things to do for PHP.next. The 64 bit support patch - there is a lot of work converting the extensions ahead, and this is DAMN IMPORTANT STUFF. Way more important than PHP Spec. The Unicode problem needs to be worked on too. The Zend Engine iteration for crying out loud - it's last big update was like what, 10 years ago? There are also interesting things happening - the Zephyr project, the PHPCC lib for extension development - these are not just standalone alternate PHP engines, these projects are directly tied with the original PHP, the one we are talking about. Establishing a dialog and collaboration can benefit PHP a lot (I dream of times when most of the PHP extensions could be written with Zephyr without touching the low-level C - certainly would make contributions much easier for many of us). Alternate PHP engines can provide ideas and insights into updating the Zend Engine. Just my 0.02$ as a userland developer, for whom the future of PHP is important :) Arvids.