use logical OR (||) instead of binary OR (|) in logical context
The compiler can short-circuit the evaluation of conditions strung together with logical OR operators instead of computing the resulting bitmask with binary ORs. More importantly, this patch makes the intent of the changed code clearer, because the logical context (as opposed to binary context) becomes immediately obvious. While we're at it, simplify the check for patch->is_rename in builtin/apply.c a bit; it can only be 0 or 1, so we don't need a comparison operator. Signed-off-by: René Scharfe <rene.scharfe@lsrfire.ath.cx> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
f2b4626d9e
commit
0b437a18bd
@ -107,7 +107,7 @@ int cmd_merge_base(int argc, const char **argv, const char *prefix)
|
||||
argc = parse_options(argc, argv, prefix, options, merge_base_usage, 0);
|
||||
if (!octopus && !reduce && argc < 2)
|
||||
usage_with_options(merge_base_usage, options);
|
||||
if (is_ancestor && (show_all | octopus | reduce))
|
||||
if (is_ancestor && (show_all || octopus || reduce))
|
||||
die("--is-ancestor cannot be used with other options");
|
||||
if (is_ancestor)
|
||||
return handle_is_ancestor(argc, argv);
|
||||
|
Reference in New Issue
Block a user