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.
>> >
> V
On 4/30/2016 11:52 PM, Rowan Collins wrote:
> Just thought I'd point out this contradiction.
>
> It seems to me that "Data Annotations" are one particular use of a
> language feature which is called "attributes". Looking through the list
> of descendants of the base Attribute class [1], I can see
On 30/04/2016 12:09, Fleshgrinder wrote:
Erm, actually I did not claim anything [...] I previously claimed that
Microsoft does a perfect job.
Just thought I'd point out this contradiction.
That claim was based on the fact that the feature is called "Data Annotations"
and that
one can apply
On 4/28/2016 9:43 PM, Rowan Collins wrote:
> I meant specifically in the context of C#/.net. You claimed a very
> specific usage within that framework, but all the articles I can find
> refer to them consistently as "attributes" in that context. Event the
> Wikipedia article:
>
>> In the C# progra
Fleshgrinder wrote on 28/04/2016 20:20:
On 4/28/2016 8:02 PM, Rowan Collins wrote:
Interesting; do you have a link to where this terminology is explained?
Most of the articles I've seen just refer to "attributes", and the link
you have doesn't really explain that at all, it has namespaces with
"
On 4/28/2016 8:02 PM, Rowan Collins wrote:
> Interesting; do you have a link to where this terminology is explained?
> Most of the articles I've seen just refer to "attributes", and the link
> you have doesn't really explain that at all, it has namespaces with
> "annotation" in the name, but uses t
Fleshgrinder wrote on 28/04/2016 18:33:
Actually Microsoft got it exactly right and they are explaining in depth
what I wrote as well. The result of an annotation is an attribute. So it
is only natural to call the classes attributes.
public class Customer {
[DataType(DataType.EmailAddre
On 4/27/2016 11:36 PM, Lester Caine wrote:
> To add to your list ...
> https://www.phpdoc.org/docs/latest/guides/docblocks.html
>
> The glossary entry is rather bare, but I would dispute THEIR statement -
> "but also influences the way the application behaves."
>
> In my book, these comment block
On 4/28/2016 11:36 AM, Rowan Collins wrote:
> While I personally prefer the name "annotations", I don't see it as
> particularly urgent, or nearly as clear-cut as you claim.
>
That's okay and why we are discussing things. ;)
On 4/28/2016 11:36 AM, Rowan Collins wrote:
> I clicked through on your
Fleshgrinder wrote on 27/04/2016 21:11:
I am writing this in a separate thread because of the urgency that I see
regarding the naming of past, current, and future proposals regarding
this functionality.
While I personally prefer the name "annotations", I don't see it as
particularly urgent, or
On 27/04/16 21:11, Fleshgrinder wrote:
> It is about natural language, proper computer
> science terminology, and what PHP users will search for in search
> engines.
To add to your list ...
https://www.phpdoc.org/docs/latest/guides/docblocks.html
The glossary entry is rather bare, but I would dis
2016-04-27 22:53 GMT+02:00 Niklas Keller :
> Fleshgrinder schrieb am Mi., 27. Apr. 2016 22:11:
>
> > I am writing this in a separate thread because of the urgency that I see
> > regarding the naming of past, current, and future proposals regarding
> > this functionality.
> >
> > It was and is pro
Fleshgrinder schrieb am Mi., 27. Apr. 2016 22:11:
> I am writing this in a separate thread because of the urgency that I see
> regarding the naming of past, current, and future proposals regarding
> this functionality.
>
> It was and is proposed to create this feature with the name *Attributes*
>
13 matches
Mail list logo
