Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104451 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 3883 invoked from network); 17 Feb 2019 03:39:13 -0000 Received: from unknown (HELO mail-40133.protonmail.ch) (185.70.40.133) by pb1.pair.com with SMTP; 17 Feb 2019 03:39:13 -0000 Date: Sun, 17 Feb 2019 00:23:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1550362992; bh=JOPAmfDsYwqjsprEr7Dvat8S8tDBFykTLRUzn9sF2lo=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=caLS8DD6pLKjquGoAGZoy03VfW4BUpB5Tzqw+w5cyCoVY4YQCmiBPfLtQfMdeKmyA YNSgNYPU7sCgci3Rn1dXYUIBfQMHWaQazZhKo5oMwsyjRvyeT/2itNpNetc/U68Vl6 RxLrenHVibEZV4kUJjv8W7UQ8Tea0kOUFB2GIu7I= To: Pierre Joye Cc: Dmitry Stogov , Kalle Sommer Nielsen , Niklas Keller , Benjamin Eberlei , PHP internals Reply-To: azjezz Message-ID: In-Reply-To: References: <24d0544c-1852-2a72-477d-e6b364dff953@zend.com> Feedback-ID: 2QbNVvXqZX7F9J8FTDAv0u3ryua4T0_lfklxZ8hRMzvBUxf8m8U50Gi9tVWG9V2LePU31MFOrVnxPKYLJjZPXw==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=0.4 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,SUBJ_ALL_CAPS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch Subject: Re: [PHP-DEV] [RFC] JIT From: azjezz@protonmail.com (azjezz) Hello internals. Sent with ProtonMail Secure Email. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Wednesday, February 6, 2019 9:23 AM, Pierre Joye = wrote: > On Wed, Feb 6, 2019 at 3:17 PM Dmitry Stogov dmitry@zend.com wrote: > > > On 2/5/19 10:31 PM, Kalle Sommer Nielsen wrote: > > > > > Den tir. 5. feb. 2019 kl. 20.48 skrev Niklas Keller me@kelunik.com: > > > > > > > Shouldn't we introduce annotations instead of relying on doc commen= ts? > > > > > > Yeah I'm not too happy with that approach either. I would rather see > > > another way to do this and like you said; annotations is probably the > > > best way to go about it as introducing a new keyword is not very > > > suitable imo. > > > > Attributes were proposed ~3 years ago. > > https://wiki.php.net/rfc/attributes > > There were few other releted proposals. > > But they didn't pass. > > Understanding and adoptions of annotations (Doctrine mainly afaics) > have change. I think it is tricky to define it in a way that it can be > useful and adopted as a core language feature, meaning being flexible > enough to be extendable and usable as a base for userland extensions. > That latter part is the biggest challenge. What do the actual > users/authors of the current userland implementation think? (pls other > thread? :) > > Best, > > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------------------------------- > > Pierre > > @pierrejoye > > -------------------- > > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php In the past few weeks i have been mainly using hack-lang and the attributes= API has changed as of 3.29 ( https://hhvm.com/blog/2018/10/22/hhvm-3.29.ht= ml - change actually landed on 4.0 instead ) and i think its a good approac= h that php can take too. I have no experience with C so i don't know how this would work out for PHP= , but i made a gist with a simple example on how it would be in : https://gist.github.com/azjezz/918e333646d4f4070ab0be4cb41a81de