Annotations are already a part of PHP. They are widely used in one of the most prolific frameworks, Symfony, and it's ORM "counterpart" Doctrine. Both of which are serious drivers of the PHP community. It's even potentially spreading to Zend Framework: http://zend-framework-community.634137.n4.nabble.com/Annotations-own-implementation-or-Doctrine-Commons-td4655427.html
To say "they shouldn't be part of PHP" is fine, but it's too late for that. Annotations are already here. Are we going to just ignore this fact and hold back what a very significant portion of the community wants to see because it conflicts with some ambiguous master plan for PHP? Cheers. On Wed, Jan 9, 2013 at 5:39 PM, Adam Harvey <ahar...@php.net> wrote: > On 10 January 2013 03:00, Anthony Ferrara <ircmax...@gmail.com> wrote: > > Well, the point is that there are two ways of voicing your dislike. You > can > > say "I never want this" or other rhetoric, which helps nobody else but to > > understand that you don't want it. Or you can be a little bit more civil > > and reply detailing your concerns, and say "Based on that, I don't like > > it". > > Amaury has a point, though. > > Personally, I don't think annotations belong in PHP. Now, I can > explain why based on my use of Symfony and Doctrine, but that suggests > that I'm going to change my mind when truthfully, I'm almost certainly > not going to — it's a difference of philosophy, rather than something > specific to the RFC or the patch. > > So my dilemma is this: how do I voice this (without simply a drive-by > -1 vote, which isn't really helpful either, and is overly discouraging > to the people who've put a lot of work in to polish the feature up) > without being shouted down for being unhelpful or uncivil? > > Adam, who isn't touching the rest of this discussion with a ten foot pole. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
