Re: [VOTE] Attribute Amendments
| From: | Benjamin Eberlei | Date: | Mon, 08 Jun 2020 19:06:09 +0000 |
| Subject: | Re: [VOTE] Attribute Amendments | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-110435@lists.php.net to get a copy of this message | ||
On Mon, Jun 8, 2020 at 6:48 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 :(
>
Ah I think i understand where you come from, the original wording from
Marco was I believe meant to explain only an analogy that <<>> can be seen
as enclosement similar to /** */ in docblocks.
>
> --
> 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
>
>