Today I found a problem regarding evaluation of logical functions and boolean va

Stefan Helzle

A Score Level 3

over 9 years ago

Today I found a problem regarding evaluation of logical functions and boolean variables with null values. The function "and(null())" evaluates to "true", "or(null())" evaluates to "false" and "not(null())" tells me that null parameters are not allow. Adding some true() or false() values to the and() and or() functions return correct values.

When I bring the if() function into play which always handles null() values to false() the whole behaviour looks quite inconsistent to me. I think that "and(null())" as well as "or(null())" should evaluate to "false". The function "not()" should take null() values as "false" and for consistency "not(null())" should evaluate to "true"....

Discussion posts and replies are publicly visible

Parents

0 Stefan Helzle
A Score Level 3
over 9 years ago

I know that documentation. I know that using an AND or an OR with only one parameter does not make much sense. My main concern is that NOT with null() throws an exception. To have a NOT function that is save I would need something like if(pv!abc, false(), true()). But do we want that?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Stefan Helzle
A Score Level 3
over 9 years ago

I know that documentation. I know that using an AND or an OR with only one parameter does not make much sense. My main concern is that NOT with null() throws an exception. To have a NOT function that is save I would need something like if(pv!abc, false(), true()). But do we want that?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data