Quote from RFC 4526:
An 'and' filter with zero elements always evaluates to True. An 'or' filter with zero elements always evaluates to False.
My question is, is there any theory this decision is based on, or is it randomly chosen?
Why not (&) being false, and (|) being true?
Or more specifically, we know 'FALSE && NULL' is FALSE, we know 'TRUE || NULL' is TRUE, but is there reason 'NULL && NULL' being true and 'NULL || NULL' being false?
Thanks:)
On 2013-08-08 06:47, Zhang Weiwu wrote:
Quote from RFC 4526:
An 'and' filter with zero elements always evaluates to True. An 'or' filter with zero elements always evaluates to False.
My question is, is there any theory this decision is based on, or is it randomly chosen?
Why not (&) being false, and (|) being true?
AND is false if there is a false component. OR is true if there is a true component.
openldap-technical@openldap.org