digitalmars.D - What is an attribute?
- Lars T. Kyllingstad (6/6) Nov 11 2009 So, it seems that @annotations will become a part of D. But which of the...
- Lars T. Kyllingstad (3/11) Nov 11 2009 Sorry, bit of a typo in the message subject there. ;)
- sclytrack (7/18) Nov 11 2009 a) Things that shows up in the reflection
- Spacen Jasset (2/30) Nov 11 2009 (c) is the one.
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
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() { ... } -LarsSorry, bit of a typo in the message subject there. ;) -Lars
Nov 11 2009
== Quote from Lars T. Kyllingstad (public kyllingen.NOSPAMnet)'s articleLars T. Kyllingstad wrote: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.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() { ... } -LarsSorry, bit of a typo in the message subject there. ;) -Lars
Nov 11 2009
sclytrack wrote:== Quote from Lars T. Kyllingstad (public kyllingen.NOSPAMnet)'s article(c) is the one.Lars T. Kyllingstad wrote: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.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() { ... } -LarsSorry, bit of a typo in the message subject there. ;) -Lars
Nov 11 2009