Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78600 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6553 invoked from network); 3 Nov 2014 22:49:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Nov 2014 22:49:57 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.43 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.218.43 mail-oi0-f43.google.com Received: from [209.85.218.43] ([209.85.218.43:49261] helo=mail-oi0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/75-10620-49608545 for ; Mon, 03 Nov 2014 17:49:57 -0500 Received: by mail-oi0-f43.google.com with SMTP id e131so9461730oig.2 for ; Mon, 03 Nov 2014 14:49:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OLVzh1gaH72OzzS1sCcS82GfJBPhGVi+Ha1SGEeZzNs=; b=MYvMSunq6+gJKExleJUjKz7Wnl9vxzQmGylZlYdQ9ai0m3xLaEajc//zSy2toKVWBl 1Ik7AUyNltKT6sobwkICPFe5vfIqwM99t2nFYwqB3zQF++b5UW/9v2Yt3GCpUAQbDt1v Ay06bhGU82GS6VBSWuUs8lFAggj6am/qa9VvxMyQKaOWVJJclgjU8tUdTdQ7DUaWB3Kx JtRvs5hglJAcn3yLO5LjvsJST9jnNG+zcOqR79P3D2lTO1eJFl6qUIytUvKFZOASlpxv htzCWkANsIN07vltPEqnRB2FTuMfEfFA0d69l3aCZeHmmFi3S70f3wXAQ051CAJQ0/Vd RC3w== MIME-Version: 1.0 X-Received: by 10.182.50.198 with SMTP id e6mr4114964obo.45.1415054994458; Mon, 03 Nov 2014 14:49:54 -0800 (PST) Sender: morrison.levi@gmail.com Received: by 10.76.159.163 with HTTP; Mon, 3 Nov 2014 14:49:54 -0800 (PST) In-Reply-To: <5457BDB7.8070701@garfieldtech.com> References: <5457AF2F.90808@php.net> <5457BDB7.8070701@garfieldtech.com> Date: Mon, 3 Nov 2014 15:49:54 -0700 X-Google-Sender-Auth: uzXlTVchsIvsGv5283VUDzZeAEE Message-ID: To: Larry Garfield Cc: internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Annotation PHP 7 From: levim@php.net (Levi Morrison) On Mon, Nov 3, 2014 at 10:39 AM, Larry Garfield wrote: > 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.) Whether the annotation is in a comment or not, the idea of changing behavior at runtime based on the annotation is pretty magical. I highly discourage using this type of feature whether it's in a comment or not. I will certainly vote no on any RFC on this subject, as I see it as being significantly more harmful than helpful.