Hi!
Last year, I attended to a conference where you (Stas) told that the best way to do a feature request/proposal was by writing a RFC and a patch even if the patch is not perfect. The current implementation may not be perfect but it was never said it was a final one. This is a proposal of a first implementation which is a start to take people's attention and feedback.
Of course, writing an RFC and a patch is a good way to start the process and I think it is great you did it. However it doesn't mean any RFC/patch will be accepted. That's why we discuss it - and there's no guarantee that the result would be acceptance. Rodin said he makes sculpture by chopping off extra pieces from the block of marble. We need to chop off stuff too sometimes if we want the language to stay easy to learn, read and use.
So the first question that we have to agree is regardless the syntax, and the entire implementation do we want to add the ability to add code metadata (like annotations) or not into PHP. My opinion is yes. If everybody finds this idea stupid then the discussion stops.
I think we _already_ have metadata in PHP, albeit done through phpdocs. So the question is kind of moot :) We should see if it's enough for us or we want to add/change/extend it and if so, how.
I however have some doubts about usefullness of "code" metadata - i.e. code being run as part of metadata processing in the language. Having purely declarative metadata you can always have user code run on it and do any logic you want, but having "active" metadata seems to me to have high potential for complications.
Speaking of syntax, I think it is important too, because syntax defines readability and usability of the language. And unobvious syntax rules for different parts of the language hurts that.
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
