www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - What is an attribute?

reply "Lars T. Kyllingstad" <public kyllingen.NOSPAMnet> writes:
So, it seems that  annotations will become a part of D. But which of the 
existing attributes should become annotations, and which should remain 
as they are? What is the rule for determining whether a new feature 
should be introduced in terms of annotations?

    safe  pure  nothrow  immutable int foo() { ... }

-Lars
Nov 11 2009
parent reply "Lars T. Kyllingstad" <public kyllingen.NOSPAMnet> writes:
Lars T. Kyllingstad wrote:

 So, it seems that  annotations will become a part of D. But which of the 
 existing attributes should become annotations, and which should remain 
 as they are? What is the rule for determining whether a new feature 
 should be introduced in terms of annotations?
 
    safe  pure  nothrow  immutable int foo() { ... }
 
 -Lars



Sorry, bit of a typo in the message subject there. ;)

-Lars
Nov 11 2009
parent reply sclytrack <Sclytrack idiot.com> writes:
== Quote from Lars T. Kyllingstad (public kyllingen.NOSPAMnet)'s article

 Lars T. Kyllingstad wrote:

 So, it seems that  annotations will become a part of D. But which of the
 existing attributes should become annotations, and which should remain
 as they are? What is the rule for determining whether a new feature
 should be introduced in terms of annotations?

    safe  pure  nothrow  immutable int foo() { ... }

 -Lars


 Sorry, bit of a typo in the message subject there. ;)
 -Lars


a) Things that shows up in the reflection

b) When added to stuff it doesn't create a new type or overload.

c) Annotations provide data about a software program that is not part of the
program itself. They have no direct effect on the operation of the code they
annotate. (wikipedia)

Pick one, ... or two.
Nov 11 2009
parent Spacen Jasset <spacenjasset yahoo.co.uk> writes:
sclytrack wrote:

 == Quote from Lars T. Kyllingstad (public kyllingen.NOSPAMnet)'s article

 Lars T. Kyllingstad wrote:

 So, it seems that  annotations will become a part of D. But which of the
 existing attributes should become annotations, and which should remain
 as they are? What is the rule for determining whether a new feature
 should be introduced in terms of annotations?

    safe  pure  nothrow  immutable int foo() { ... }

 -Lars


 Sorry, bit of a typo in the message subject there. ;)
 -Lars


 
 a) Things that shows up in the reflection
 
 b) When added to stuff it doesn't create a new type or overload.
 
 c) Annotations provide data about a software program that is not part of the
 program itself. They have no direct effect on the operation of the code they
 annotate. (wikipedia)
 
 Pick one, ... or two.
 
 
 
 
 
 


(c) is the one.
Nov 11 2009