On 05/22/10 09:35 AM, Felix Feng wrote:
于 2010-5-22 00:19, Garrett D'Amore 写�:
Does it make sense to use some special value (zero or -1) to mean
uninitialized? That way could at least preserve the type.
But the special value is invalid for keyboard configurations. If it is
set in keyboard properties, users may get confused. So I prefer 'null'
to mean uninitialized. Thanks.
This is a valid point. However, if I understood correctly, these are
values set in the SMF manifest. You can have comments in the manifest
explaining the uninitialized value. Moreover, you can leverage SMF
templates to validate the values, but if you use astring, you cannot
validate ranges.
I don't understand why a missing value in the SMF repository can not be
inferred as uninitialized. Could you please elaborate that?
Antonello
_______________________________________________
opensolaris-arc mailing list
[email protected]
