Menu
Is there any merit to using a nullable bool to store a tri-state value? For example, null == 1st state, false == 2nd state, true == 3rd state?
The overhead is probably higher than using a byte enum, but I'm curious.
616
You typically use a nullable value type when you need to represent the undefined value of an underlying value type. For example, a Boolean, or bool , variable can only be either true or false . However, in some applications a variable value can be undefined or missing.
Amongst other, more important distinctions, value types, such as bool or int, cannot contain null values.
It be that you need to test if SessionManager is null before you access it, or maybe the HoldStringId needs to be tested for null, as well as that. Nullable types can be checked using the HasValue property, and their value can be retrieved with the Value property.
You should get a copy of Framework Design Guidelines.
There on page 177 is a chapter Choosing Between Enum and Boolean Parameters.
One of the points there is:
125
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
