Hi!
I mean that any code packer can degrade the the functionality of your app. Example:
Fix your "code packer" not to do that.
I didn't mean we should stop the discussion. I meant that like many others over the years lead to nowhere if we don't take the correct action: vote.
How it's the correct action on this stage? We obviously don't have consensus on what this feature should be - we are just looking for a possible solution now. How voting can help? People would just say "yes, I want Annotations" while meaning totally different things by it (or without really understanding what they vote for/against). How that's useful?
So I'd recommend (although I didn't like how it was written) the Java Annotation wikipedia page: http://en.wikipedia.org/wiki/Java_annotation
So, we are voting to have Java annotations in PHP? And people seriously voting FOR it? I mean, after reading all 40+ disjoint pages of the standard describing it in Java, and considering how that would fit PHP, they make an informed decision that that's exactly what PHP needs right now, correct?
-- 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
