Talk:Transient Attributes

Revision as of 08:19, 6 July 2009 by Manus (Talk | contribs) (Talk:Volatile Attributes moved to Talk:Transient Attributes: Better naming of mechanism)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

--Alexander Kogtenkov 15:28, 30 June 2009 (UTC) What happens when the attribute is inherited? It is still possible to inherit the volatile attribute in an expanded class. Or does the volatile property work only in the class it is declared, i.e. the property of being volatile is not inherited?

--manus 15:06, 1 July 2009 (UTC) The validity rules are applied for inherited attributes as well, and the volatile property is inherited. In order to not inherit it, you have to redefine the attribute.
--Alexander Kogtenkov 16:16, 1 July 2009 (UTC) In other words, an expanded class has to redefine any attributes declared in parent class as volatile, right?

--Clemahieu 16:07, 1 July 2009 (UTC) What are the semantics around a note clause under an attribute? This looks like a weaker form of C# attributes, is this intended to be a one-off things for serialization? EDIT: Are these only accessible within the compiler or are they accessible programatically?

--Peter gummer 23:18, 1 July 2009 (UTC) No, it's not a one-off. Eiffel for .NET already uses note to decorate features, etc. with .NET "attributes". (Why oh why did the designers of .NET choose to use the word "attribute" for their metadata tags?)

--Alexander Kogtenkov 08:41, 2 July 2009 (UTC) It might make sense to mark the attributes as transient instead to be in line with other software.