On Mon, May 9, 2011 at 6:55 PM, Marcelo Gornstein <marce...@gmail.com> wrote: > regarding the annotations stuff: it seems the php community (in > general) really wants annotations. lots of important and widely used > frameworks use them (meaning that not only the plain php users have a > use for this feature, but also the users of the respective frameworks, > increasing the overall user number interested). i.e: doctrine, > symfony2, ding, phpunit, etc, etc. we cant just ignore this fact. > > also, this means that there are tons of custom annotations > implementations (almost one per framework that has a use for them), > and we end up duplicating code and slowing the overall performance > for applications. > > my question is: is php a language made for the php developers that > mantain the language or for the community that uses them and > contributes to it everyday?
I don't know if annotations are *needed* in PHP 5.4. There are a few libraries, out there, that can help developers, as you said, from now. Doctrine's one it's really powerful, and you can clone the repo from github and easily start using the annotation library. So my point is to say that, although *we need a unified way to manage annotations* ( for the reasons Marcelo just explained ), they don't need to be a focus point for PHP 5.4. > > just a thought > > On Mon, May 9, 2011 at 1:44 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote: >> On 05/09/2011 07:44 AM, guilhermebla...@gmail.com wrote: >>> >>> - Annotations >>> >>> I already proposed a patch and none here discussed. You rather >>> preferred to shout "PHP doesn't need Annotations" instead of discuss >>> the patch that was proposed. >> >> If someone doesn't agree that annotations belong in PHP why do the details >> of the patch matter? >> >>> PS: I think that internals mailing list should be revised with all >>> proposed ideas and wrap them on a better plan. >>> It seems to me that you are not interested on user's request and >>> rather accept/implement only what the features that interest you. It's >>> very bad for the language and very bad for all of users. >> >> That's simply not true. But just because one group of users feel strongly >> about something doesn't mean it should go in. There has to be some level of >> curation or we end up with every feature under the sun resulting in a huge >> mess. >> >> -Rasmus >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > > > -- > > -- > // I don't sleep. I coffee. > "Make everything as simple as possible, but not simpler." -- Albert Einstein > "The class object inherits from Chuck Norris." > "Chuck Norris can divide by zero and can unit test an entire > application with a single assert." > "There’s a lot of work happening behind the scenes, courtesy of the > Spring AOP framework" > "Why do I have this nagging hunch that you have no idea what you're doing?" > "Any society that would give up a little liberty to gain a little > security will deserve neither and lose both" - Benjamin Franklin > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Nadalin Alessandro www.odino.org www.twitter.com/_odino_ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
