Re: Re: PHP Annotations RFC + Patch

From:	Stas Malyshev	Date:	Thu, 16 Sep 2010 19:27:19 +0000
Subject:	Re: Re: PHP Annotations RFC + Patch
References:	1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18	Groups:	php.internals
Request:	Send a blank email to internals+get-49728@lists.php.net to get a copy of this message

Hi!

Overloading comment syntax to modify application functionality is the worst idea I've seen suggested on this list. This beats goto by miles.

What you mean "suggested"? It's what happening right now in pretty much any widely used framework.

"Why's my stuff broke? That stack trace leads me through... a docblock?!? Wait, that comment I updated wasn't really a comment, it

That's why code annotations are bad idea. Metadata should not be code. And in Java, for example, annotations are interfaces.

just looked like one? Oh hell, that other comment I added got mistaken for an annotation? WTF?" This is supposed to be *less* confusing for people?

Nothing can un-confuse person that deliberately tries to be confused. You are fighting a strawman - nobody suggests having active code in comments. Metadata is not code - it's data. Backtraces can't lead to data. You can store data in a variety of formats - what is suggested (and already is widely used) is just yet another format to store/retrieve data. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227