Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52271 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38545 invoked from network); 11 May 2011 06:50:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2011 06:50:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=dukeofgaming@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dukeofgaming@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: dukeofgaming@gmail.com X-Host-Fingerprint: 74.125.83.42 mail-gw0-f42.google.com Received: from [74.125.83.42] ([74.125.83.42:39443] helo=mail-gw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/10-37490-1C13ACD4 for ; Wed, 11 May 2011 02:50:42 -0400 Received: by gwb17 with SMTP id 17so84841gwb.29 for ; Tue, 10 May 2011 23:50:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ZI2cNXThe2dz4I2yIL3Gffeh65ooAGEZr1470Lhq9Cc=; b=tBh8I2KHLSJLRbHap/MdfIGmIwoO5Aev18v3ptOHNx4zGLBnfvUrs5zb+Q9z26Sonn G9+ERhQj8zEuikb/gkwHFC7u2B4dwir3eC/f4OjdIejBs2PWBCbc0qGUq0xqkwoxWwrY 1W2jqrZKECm21HukvfnhHZ2h+lSP41d3NdpRE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=UZUV6qdoQCFZ8DGj7diOtZSskVS2fZGDyu+lxaa2+lA3LtS0O9hfvPH/NrqTbQDa1n SWecVHjknQ0LTO4moT43FPIiGTUBnhQhjOGw+YZWD6x9zSoJSqUqvDq+8OSx5psCKxia gZQXe8lXlvJxJjO5V2R1RL2/YrzaWkY+QIAIM= Received: by 10.101.9.3 with SMTP id m3mr5654623ani.17.1305096639266; Tue, 10 May 2011 23:50:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.108.6 with HTTP; Tue, 10 May 2011 23:50:19 -0700 (PDT) In-Reply-To: <4DCA2192.4080201@lsces.co.uk> References: <4DC729EE.9090600@sugarcrm.com> <4DC75FFF.40008@lerdorf.com> <4DC7A7F0.4000504@sugarcrm.com> <4DC819D0.5010008@lerdorf.com> <4DC81ED6.1050902@sugarcrm.com> <8757232E56758B42B2EE4F9D2CA019C9013F9F59@US-EX2.zend.net> <4DCA2192.4080201@lsces.co.uk> Date: Wed, 11 May 2011 01:50:19 -0500 Message-ID: To: Lester Caine Cc: PHP internals Content-Type: multipart/alternative; boundary=0016e6d260d294be9504a2fa7db4 Subject: Re: [PHP-DEV] annotations again From: dukeofgaming@gmail.com (dukeofgaming) --0016e6d260d294be9504a2fa7db4 Content-Type: text/plain; charset=ISO-8859-1 Hi, On Wed, May 11, 2011 at 12:41 AM, Lester Caine wrote: > guilhermeblanco@gmail.com wrote: > >> So, please stop saying "no" to every feature request that comes in and >> start to discuss the actual impact of each feature. >> > > I think that MY only problem with you 'adding annotations because it is > missing' is simply that I've already been doing it for years - just not > calling it 'annotations' ... its 'documentation' and always has been ... > It is really troubling to read that statement. Seems there are still some that don't really have a clue of what annotations are, even when the RFC clearly links to them. Annotations ARE NOT documentation; in the case of PHP, documentation is being used as annotations because there is no language implementation, which exists in other languages (Java, .NET) and they are widely used. Also, some use annotations as documentation (e.g. store the class version), but again, annotations ARE NOT documentation. Don't let the "@" notation shared with docblock fool you. Guilherme, I think its easy to assume that people already have some sense of what annotations are, but perhaps the wiki entry could be more educational about it?. The first time I read about annotations it was from this link: http://download.oracle.com/javase/tutorial/java/javaOO/annotations.html; perhaps an intro like that could help to make the case for annotations crystal clear?. > > The real problem at present is that the whole ecosystem is now so > disjointed that PHP5.2 is the last version that is still fairly fully > supported, but people are pushing for 5.4 before 5.3 has been properly put > to bed. We need to finish of what is already added fully before pushing more > new stuff in? That INCLUDES in the ecosystem! > > And we still have the hole that is unicode ... > This is another thing that troubles me when I read this list. How does the PHP core dev community sets priorities?, is there some sort of roadmap?, is there a process to create this roadmap?, or is it just all a generalized best intention to do things. I'm aware that the more features the more has to be maintained, but, what I see is that there is lot of potential for the core dev community to grow and at its current state it doesn't seem to be able scale due to the lack of a roadmap/process. I'm not trying to be a douche here, just saying: I see lots of criticism towards everything and very few agreements. Best regards, David Vega --0016e6d260d294be9504a2fa7db4--