[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.20.1703281555450.21255@n3.vanv.qr>
Date: Tue, 28 Mar 2017 16:03:09 +0200 (CEST)
From: Jan Engelhardt <jengelh@...i.de>
To: simran singhal <singhalsimran0@...il.com>
cc: pablo@...filter.org, outreachy-kernel@...glegroups.com,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
"David S. Miller" <davem@...emloft.net>,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] netfilter: ipset: Use max macro instead of ternary
operator
On Tuesday 2017-03-28 15:32, simran singhal wrote:
>This patch replaces ternary operator with macro max as it shorter and
>thus increases code readability.
>
>- return (ret < 0 ? 0 : ret);
>+ return max(0, ret);
While the two are functionally equivalent, "max" conveys a meaning of
"upper bound" (think ceil(3)), i.e. a _count of something_, but the
function still returns a logical "error or bool".
Such a change may be usable in an IOCCC or a codegolf contest,
but it destroys rather than improves readability IMHO.
Powered by blists - more mailing lists