coverity: merge traverse{OR,AND}Criteria into traverseSearchCondition
Meaning, these two functions have the same behaviour, they produce the same output (and side-effects) when called on the same input. traverseORCriteria handles only the actual "foo OR bar" case, and hands off all other cases to traverseANDCriteria. But, lo and behold, traverseANDCriteria also handles the "foo OR bar" case, in the same manner! Change-Id: I10410e88ce48852b60d1d688fe2865923de9d80b
Showing
Please
register
or
sign in
to comment