Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93207 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96928 invoked from network); 11 May 2016 06:57:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2016 06:57:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.161.180 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.161.180 mail-yw0-f180.google.com Received: from [209.85.161.180] ([209.85.161.180:32933] helo=mail-yw0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/A0-28272-AC7D2375 for ; Wed, 11 May 2016 02:57:14 -0400 Received: by mail-yw0-f180.google.com with SMTP id t10so38625986ywa.0 for ; Tue, 10 May 2016 23:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pthreads-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=kM0KGbfuRm8b6s13hpNxFhUPJnICjBjxkhYDJ4UpAKU=; b=iBII/E9qbybVYbnsUajtX96SfpI65IvvtFOtGGcVvkk07Yp2DWtPLyd7SJ9EBXUPen 6khHq3dahPKuta3Q7ifdkilituB5SFhIiujPj+tnp/SOQq8evPXGKeyKB9Mzu60HNQ6m qAtNcY8TU9HVClLpClplLd1WsQgwVt60loGWkOyoQeatEzLRDAn8HFNmNVUScltvTk4q J580cjTsd+x5d1OVAawtI1ifizDpPaps2in6CoquOar3CmJv2SN3fAmRdLUs8vuthVyP xEQxn5Vwq7sn8m4LnULHDHLXVuJgSLotpPnttGC7QHOrjaTd+vdkIrTMslLy7emiZ2jP sYbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=kM0KGbfuRm8b6s13hpNxFhUPJnICjBjxkhYDJ4UpAKU=; b=OURTWNQ370yYGAtxKYJViAjML6+on4cTTGtN59z0BA1fqUFANiknkEWQMz1mZBng8l RZxBtt7JofR2eGry3SX/HJo2rp8oAQUmYhs4h+O3AeUpQfcwMqdlspljxt2ehULTU+da jm//uLVJqQx3bkzYdcpKr5zq51hdAGFwiHRMEDq+wdK32+UFGZKWXTlzjAOp95sOBTbT AXnVG5BAc8r9tsmiBbduc5UZQSYV+zU8jgvcKWRY12L9TTYxoL8iRmPW7+dsyL5GO6fh nJNTodlK0hhfIwVnSoN5GmnHfJhfdLXy/Bv3SHLPjqGvAGOgcEbGA9fWdcF81M9l9sQQ q7Gw== X-Gm-Message-State: AOPr4FUizd6q4tSs1swwCBXoVxfL7mbvwad8L5nnKf4+70xskoK66bc6X1xGWwQkRnuL7y4qItRvxf/JjTSrnQ== MIME-Version: 1.0 X-Received: by 10.37.209.132 with SMTP id i126mr653044ybg.79.1462949831012; Tue, 10 May 2016 23:57:11 -0700 (PDT) Received: by 10.129.109.67 with HTTP; Tue, 10 May 2016 23:57:10 -0700 (PDT) X-Originating-IP: [165.120.173.102] In-Reply-To: <95ccaf31-11de-8efb-13ba-038d36a6c466@zend.com> References: <8d5d1c42-832d-4406-6bb5-dbf3fc02c364@telia.com> <95ccaf31-11de-8efb-13ba-038d36a6c466@zend.com> Date: Wed, 11 May 2016 07:57:10 +0100 Message-ID: To: Dmitry Stogov Cc: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= , PHP internals Content-Type: multipart/alternative; boundary=94eb2c06b32e00a3e105328b8d31 Subject: Re: [PHP-DEV] [RFC] [VOTE] PHP Attributes From: pthreads@pthreads.org (Joe Watkins) --94eb2c06b32e00a3e105328b8d31 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dmitry, > but it's possible to get the same power translating string values of attributes into AST in the hooks. Aware. Enough of the complexity is already the responsibility of the consumer of the attributes. It's already possible to get strings (and so AST) from doc comments, we don't need anything new if that's all you want to do. Essentially, moving something from doc comments to <> makes zero sense to me. Cheers Joe On Wed, May 11, 2016 at 7:45 AM, Dmitry Stogov wrote: > > > On 05/11/2016 09:02 AM, Joe Watkins wrote: > > Morning Dmitry, > > > On the other hand simple string may be parsed into AST with just one > additional call to ast\compile_string(). > > You're not really suggesting that I write my tools in user land, are you = ? > It's me, Joe :)ce > > > At first days of RFC discussion Sara pointed on over-design regarding AST= . > I saw sense in here comments and updated RFC. > > > I *only* want attributes as they were originally proposed, and I can't > vote to reflect that. > > As discussed in private, what I want is attributes, as originally > proposed, and a hookable compiler; Anything else is not good enough. > > > Personally, I'm for AST as well, but it's possible to get the same power > translating string values of attributes into AST in the hooks. > > Thanks. Dmitry. > > > > Cheers > Joe > > > > On Wed, May 11, 2016 at 6:26 AM, Dmitry Stogov wrote: > >> Hi Joe, >> >> The sense in native support for AST is questionable. >> >> >> On one hand this allows syntax verification. >> >> >> On the other hand simple string may be parsed into AST with just one >> additional call to ast\compile_string(). >> >> >> Thanks. Dmitry. >> >> >> ------------------------------ >> *From:* Joe Watkins >> *Sent:* Wednesday, May 11, 2016 7:46:09 AM >> *To:* Bj=C3=B6rn Larsson >> *Cc:* Dmitry Stogov; PHP internals >> *Subject:* Re: [PHP-DEV] [RFC] [VOTE] PHP Attributes >> >> Morning Dmitry, >> >> I'm not really happy with the voting options here. >> >> I would not vote in favour of a patch that does not include support >> for AST, that's a completely different feature. >> >> As it is, I have to vote yes in favour of AST, but it may be counted >> as a vote in favour of attributes without AST ... >> >> This doesn't seem right ... I don't want attributes without AST, and >> there is no voting option to reflect that. >> >> Cheers >> Joe >> >> On Tue, May 10, 2016 at 11:09 PM, Bj=C3=B6rn Larsson < >> bjorn.x.larsson@telia.com> wrote: >> >>> Den 2016-05-11 kl. 00:00, skrev Dmitry Stogov: >>> >>>> >>>> >>>> On 05/11/2016 12:29 AM, Bj=C3=B6rn Larsson wrote: >>>> >>>>> Den 2016-05-10 kl. 20:29, skrev Dmitry Stogov: >>>>> >>>>> Hi internals, >>>>>> >>>>>> >>>>>> I've started voting on "PHP Attributes" RFC. >>>>>> >>>>>> >>>>>> https://wiki.php.net/rfc/attributes >>>>>> >>>>>> >>>>>> In my opinion, "PHP Attributes" might be a smart tool for PHP >>>>>> extension, but it's not going to be the end of the world, if we deci= ded to >>>>>> live with doc-comments only. >>>>>> >>>>>> >>>>>> Thanks. Dmitry. >>>>>> >>>>>> Thanks for the good work. Regarding naming, I googled >>>>> "PHP attributes" vs "PHP annotations" and looking at the >>>>> result, my view is that that Annotation is a better naming >>>>> then Attributes. Any hope in changing it? >>>>> >>>> >>>> The more I listen to arguments of adepts of existing PHP annotation >>>> systems, the more I think, that "PHP attributes" is the right name for= this >>>> proposal. >>>> This feature is not just for PHP annotation systems. >>>> >>> >>> Thats a fair point, so Annotation it's not. Still, when I hear PHP >>> attributes I associate it with class / function attributes. Maybe >>> just a question getting used to the naming. Hm, wonder if PHP >>> directives could have been an option? >>> >>> Regards //Bj=C3=B6rn >>> >>> >>> >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: >>> http://www.php.net/unsub.php >>> >>> >> > > --94eb2c06b32e00a3e105328b8d31--