On 01/05/16 11:19, Fleshgrinder wrote: >> Both terms have advantages and disadvantages, precedents and >> > connotations - and both have potential ambiguities with other uses of >> > the normal English words that have been borrowed. In the end, it really >> > is mostly a matter of taste. >> > > Very true but the last sentence is not in my book; maybe in .NET, Perl, > and Hack. > > I guess we can summarize: > > - .NET world, Perl, and Hack are different than others. > - Rust is complicated and is definitely different than others. > - All others use the term according to most/all dictionaries. > > - Richard thinks annotations is the correct term. [1] > - Rowan likes annotations but thinks attributes are equally suited. > > I can live with that. Anyone can read our discussion and make up their > mind on their own (and hopefully share it with us).
My own 'working process' has always looked at annotation as the block of tags being added to an object. Then calling some elements of the annotation 'attributes' just dovetails in, just as other annotation may highlight access control or authorship. I've never though as the whole lot as individual attributes. > [1] Unless of course---and I wrote that before---we extend the name of > the new functionality to be more precise: > > - Attribute Grammar (what the current proposal effectively is) > - Meta-Attributes > - Custom Attributes > - Annotation Attributes > - Aspects [2] > - ... Which simply highlights a working practice we have been following since docBloc annotation started? What *IS* now making a lot more sense to me is the way things that I've followed the practices inherited from the original PHP4 code have been morphed into things like 'reflections'. I still don't see the entire need for this layer of complexity, and the Drupal comment that they don't use them makes sense since their code base pre-dates the need and uses 'more traditional' methods to provide the same results? If you have never had the need for reflections adding their use is a strain. If a variable is public, but should only be accessible via other functions such as getter and setter then the underlying value variable needs to be private? So if all the values are private and wrapped in code, then any value can be extended to also provide additional metadata? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
