Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89451 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51706 invoked from network); 26 Nov 2015 16:58:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Nov 2015 16:58:55 -0000 Authentication-Results: pb1.pair.com header.from=t.carnage@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=t.carnage@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: t.carnage@gmail.com X-Host-Fingerprint: 74.125.82.50 mail-wm0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:34534] helo=mail-wm0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/B2-35358-D4A37565 for ; Thu, 26 Nov 2015 11:58:53 -0500 Received: by wmvv187 with SMTP id v187so39521945wmv.1 for ; Thu, 26 Nov 2015 08:58:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=48/Sa74ep8L4cC+8i+prgl93tjR0V4bVlS6Yg/NoQd4=; b=qqa/iCmBb6SV+cw4E6oLOiL8pnifAKV8RNDF4AVoeJZgSZ8Py0L5rNMcwMH+BOlvZ9 OhzmVhwrLQ0xHQBhsc99A7MyOcIS/p80TjesR27mklSGZZSLBB/TAFtU9r1LXSI8Kx1u nHZBqeyYGZL4XkK+Tpk8nO2aQ1YJZwjkHsI8W4vkA5WUUSpnpE8TUXdFGHaUSRokoM/3 BxGjsBLIP8jtmqVLU7CQVl6gkVwMdFo5iQEZsPawWo3u+xN5Cky+SDGFG9JYfj/c+fL1 Ygj/KPH2GjW7ta5zfdgINSWC2CgBNQ7ZR9a4v2KOA1dYgzRq3Lontn9/lfOh3VfeyClZ pY2A== MIME-Version: 1.0 X-Received: by 10.194.203.99 with SMTP id kp3mr8428847wjc.3.1448557130339; Thu, 26 Nov 2015 08:58:50 -0800 (PST) Received: by 10.194.115.67 with HTTP; Thu, 26 Nov 2015 08:58:50 -0800 (PST) In-Reply-To: References: <5655D82A.8020304@lsces.co.uk> <5655E4E4.8070200@garfieldtech.com> <5655E61E.3000904@gmail.com> <5655E93F.90506@gmail.com> <5655F24B.6020401@garfieldtech.com> <5655F47C.3060504@gmail.com> <1B1E6CD7-2378-43CA-A636-83383707AF8E@gmail.com> <56572AEE.9030407@gmail.com> Date: Thu, 26 Nov 2015 16:58:50 +0000 Message-ID: To: "guilhermeblanco@gmail.com" Cc: Rowan Collins , PHP internals Content-Type: multipart/alternative; boundary=047d7bd91af230db740525747dac Subject: Re: [PHP-DEV] Native Annotation Syntax From: t.carnage@gmail.com (Chris Riley) --047d7bd91af230db740525747dac Content-Type: text/plain; charset=UTF-8 On 26 November 2015 at 16:05, guilhermeblanco@gmail.com < guilhermeblanco@gmail.com> wrote: > Ok then. I'll pretend that lack of interest didn't happen many other > situations (like http://marc.info/?t=144608767800001) and move on. > > I don't want to bring the patch up to date/simplify it without a clear > decision of at least be willing to discuss the patch and not reject by all > means. > I'd propose a voting as "Are you ready for Annotations yet?". Every core > developer understands (and can base their decisions) by looking at the > complexity of the old patch. > > Once voting completes and IF it gets approved, I'll gladly put it up to > date for consideration and update the RFC. > > []s, > > On Thu, Nov 26, 2015 at 10:53 AM, Rowan Collins > wrote: > > > guilhermeblanco@gmail.com wrote on 26/11/2015 15:14: > > > >> I haven't seen any user asking for traits > >> > > > > Just because you didn't see it, doesn't mean it didn't happen. > > > > I just did a very quick search on Google for php + mixins, limited to > 2007 > > or earlier (long before the current Trait implementation was born), and > got > > plenty of results lamenting the lack of support for horizontal reuse in > PHP. > > > > See for yourself: > > > https://encrypted.google.com/search?q=php+%22horizontal+reuse%22&safe=active&hl=en&source=lnt&tbs=cdr%3A1%2Ccd_min%3A%2Ccd_max%3A12%2F31%2F2007&tbm=#safe=active&hl=en&tbs=cdr:1%2Ccd_max:12%2F31%2F2007&q=php+mixins > > > > It's a common accusation of projects like this that time was spent on X > > that should have been spent on Y, but that's nearly always a massive > > over-simplification. > > > > Let's not spend too much time worrying if specific people are interested > - > > they may just be on holiday, or busy elsewhere, or just not have much to > > say until someone assembles a few more details about the proposed > feature. > > Keep it constructive, lay out how you think the feature should look and > > why, what questions are still open, and see what's needed to move it > > forward. > > > > > > Regards, > > -- > > Rowan Collins > > [IMSoP] > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > -- > Guilherme Blanco > MSN: guilhermeblanco@hotmail.com > GTalk: guilhermeblanco > Toronto - ON/Canada > Given that a lot of userland people have voting rights; I would suspect that an annotations rfc would pass, provided it met the needs of these users. As far as docblocks vs native goes - you've convinced me that native would be best, previously I'd have been more in favour of adding a getAnnotations method to ReflectionClass/Method/Property, to pull in annotations from docblocks. I'd like to see this goto a new RFC here are some questions though: - Can annotations be applied to functions? - Class constants? - Should annotations be a special type eg annotation Foo{} or just a class? - Do we want to add decorator support at the same time? ( http://thecodeship.com/patterns/guide-to-python-function-decorators/) --047d7bd91af230db740525747dac--