-
Key: MOF24-19
-
Legacy Issue Number: 8269
-
Status: closed
-
Source: Adaptive ( Mr. Pete Rivett)
-
Summary:
In ptc/04-10-05, section 9.1, the documentation for isSet() states that it "returns true if the value of the Property is different than the default value of that property. "
However later on in the section under Semantics, it states:If a single-valued property has a default:
....
- If the value of that property is later explicitly set, even to the default value, isSet=true,
Thus there is an inconsistency as to the value if isSet() in the case where the property has been explicitly set to a value that happens to be the same as its default.
-
Reported: MOF 1.4 — Fri, 11 Feb 2005 05:00 GMT
-
Disposition: Resolved — MOF 2.4
-
Disposition Summary:
It’s important to note that Property::default is used only for initial assignment on element creation, not as the value returned in absence of an explicit value.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
MOF24 — MOF 2.0 Core: Inconsistency about use of defaults
- Key: MOF24-19
- OMG Task Force: MOF 2 Core RTF