-
Key: MOF14-17
-
Legacy Issue Number: 4419
-
Status: open
-
Source: DSTC ( Stephen Crawley)
-
Summary:
It can be argued that there is no need to allow null as a valid value
for a Class instance. The possibility of null means that mapped APIs
need to be more complicated; e.g. the IDL "unset_*" operations. This
issue proposes that 'null' should be disallowed, making Class instances
consistent with DataType instances. The IDL mapping could also be
simplified. -
Reported: MOF 1.3 — Wed, 25 Jul 2001 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:58 GMT