Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110434
MIME-Version: 1.0
References: <CAEPJdu=e8ikF4fV0tDmSKVkBWOz1TuYTaAQ3+Yj4ohYyqn48Tw@mail.gmail.com>
 <CADyq6sJOcyuz2Aw6XzdATtDe4DLJc1FbybJi9Jnq8nVSH9-Vhw@mail.gmail.com>
 <c78de035-38a5-f57f-9ecd-a2eb5e553213@lsces.uk> <CAEPJdunuu8Y6v_bie-g1BuWtZ9kWbMApNcMW4UejQHQajDLgzQ@mail.gmail.com>
 <732f2e74-ff08-5353-7fb4-c9ab7e33b7f5@lsces.uk>
In-Reply-To: <732f2e74-ff08-5353-7fb4-c9ab7e33b7f5@lsces.uk>
Date: Mon, 8 Jun 2020 21:41:16 +0300
Message-ID: <CANeKSiT7sLGH3L-48PyGsignHPoum0FCSFrOBn2t09EWvJNWyg@mail.gmail.com>
To: Lester Caine <lester@lsces.uk>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008a946205a796f5ae"
Subject: Re: [PHP-DEV] [VOTE] Attribute Amendments
From: benas.molis.iml@gmail.com (Benas IML)

--0000000000008a946205a796f5ae
Content-Type: text/plain; charset="UTF-8"

Hey,

I'm not sure what you're referring to as "generic variable system" but
given that you mentioned "type", I assume you mean typed variables? If so,
PHP is never going to have typed variables due to performance implications.

As for the `/**` and `*/`, I believe Marco was talking about Doctrine
Annotations. For example, instead of writing this:

```
/**
 * @Route("/users", methods={"GET"})
 * @OtherAnnotation
 */
```

...we would write:

```
<<
    Route("/users", ["GET"]),
    OtherAnnotation
>>
```

Best regards,
Benas

On Mon, Jun 8, 2020, 7:47 PM Lester Caine <lester@lsces.uk> wrote:

> On 08/06/2020 16:30, Benjamin Eberlei wrote:
> >
> >
> > On Mon, Jun 8, 2020 at 11:11 AM Lester Caine <lester@lsces.uk
> > <mailto:lester@lsces.uk>> wrote:
> >
> >     On 08/06/2020 09:44, Marco Pivetta wrote:
> >      > I was mostly conflicted around the "allow grouped attributes"
> >     bit, but
> >      > James Titcumb (who currently cannot write to this list due to
> bounced
> >      > emails) convinced me that it is a good replacement for `/**` and
> >     `*/`:
> >
> >     If twenty years of documentation provided by docblocks is to be
> >     replaced
> >     there has to be a compelling reason to do so and while this latest
> >     drive
> >     for yet another documentation method seems to be now a fate acompli
> >     there WAS no reason to replace that perfectly acceptable
> documentation!
> >
> >
> > Attributes are not documentation (they could theoretically be used for
> > it, but its not the intented use-case).
> >
> > Attributes are supposed to be used with Runtime Reflection to have an
> > effect on the program.
> >
> > Their existence does not supersede docblocks, only the use of docblocks
> > for meta-programming (essentially doing what Attributes allows with
> > docblocks).
>
> So the statement that "it is a good replacement for `/**` and `*/`" is
> not correct ... it may be that others do not understand the difference?
> Personally none of this is addressing the fundamental problem of
> providing a generic variable system that can manage range as well as
> 'type' ... something the docblock have been providing for a long time
> and moving part of that to some new element is only making things worse :(
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - https://lsces.uk/wiki/Contact
> L.S.Caine Electronic Services - https://lsces.uk
> Model Engineers Digital Workshop - https://medw.uk
> Rainbow Digital Media - https://rainbowdigitalmedia.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000008a946205a796f5ae--