Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78583 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67348 invoked from network); 3 Nov 2014 17:39:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Nov 2014 17:39:08 -0000 Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.27 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.27 out3-smtp.messagingengine.com Received: from [66.111.4.27] ([66.111.4.27:56093] helo=out3-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 15/D1-57494-ABDB7545 for ; Mon, 03 Nov 2014 12:39:06 -0500 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9E7B0209F9 for ; Mon, 3 Nov 2014 12:39:03 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 03 Nov 2014 12:39:03 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:message-id:date:from :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=OuhUJOicFTye4G/+u+W84h S5NBA=; b=rurOAfWSITszxzmCUTTPusjf3jVTz1/oWZauukPXe0jYoHWW4E29RS RrxhMn3cBi0rhhngrvl5eNUQTPg59sDme1ZNsKpZeq6A+l9MV9LA32H+ftUJouig c5Gm4FrrAszeD5N7LhJBPZ3gi8nreE8wJo+9NtNAQ7sz1LCVo2RkA= X-Sasl-enc: t91GBBsy2SbmntcIWxBh7Ltv3BK1BsmwGQhhoyzq6mqf 1415036343 Received: from Palantirs-MacBook-Pro-5.local (unknown [63.250.249.138]) by mail.messagingengine.com (Postfix) with ESMTPA id 64372C0000E for ; Mon, 3 Nov 2014 12:39:03 -0500 (EST) Message-ID: <5457BDB7.8070701@garfieldtech.com> Date: Mon, 03 Nov 2014 11:39:03 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: internals@lists.php.net References: <5457AF2F.90808@php.net> In-Reply-To: <5457AF2F.90808@php.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Annotation PHP 7 From: larry@garfieldtech.com (Larry Garfield) On 11/3/14, 10:37 AM, Stefan Neufeind wrote: > On 11/03/2014 05:26 PM, Pierre Joye wrote: >> On Nov 4, 2014 1:24 AM, "Jonah H. Harris" wrote: >>> >>> On Mon, Nov 3, 2014 at 9:11 AM, Chris Wright wrote: >>> >>>> There are no current concrete plans and currently nothing being >> seriously >>>> discussed (at least, not publicly; I don't know if anyone has anything >> in >>>> pipeline that they haven't announced yet). The three RFCs you linked >> above >>>> are all basically dead. >>>> >>>> You are of course welcome to put together a proposal and/or start up a >>>> discussion on the subject if it is something you would be prepared to >> put >>>> work into. >>>> >>> >>> I, for one, severely dislike annotations. But, that's why there's an RFC >>> process :) >> >> I tend to think it is not a taste matter anymore. Symfony ecosystem >> (components, doctrine and co), Zend framework, etc use them. We see >> requests to work around user land implementation but we keep us away to get >> native support. Maybe it is time to the jump and get rid of our tastes, >> like years ago when we discussed which kind of OO we wanted in php. At the >> end of the day we do what we did not want back then. > > The TYPO3-family (TYPO3 CMS, Flow, Neos) also use annotations. > So, yes it is used "in the wild" already and is there to stay. We can > imho just make it a bit easier to work with (maybe also performance-wise > in some cases) etc. > > > Kind regards, > Stefan Drupal is now using annotations as well; not for the Symfony code we've inherited, actually, but for some home-grown systems for which we're using Doctrine's annotation library. Having first-class language support for metadata on definitions would be quite helpful, if for no other reason than native syntax checking and code assistance. (And to help people get over the "it's code in comments!!!" problem, which is entirely because we have to put annotations in comments now as a hack due to the lack of native support.) --Larry Garfield