Be more systematic about parens in C source code

Be more systematic about putting space before paren in calls,
and in avoiding unnecessary parentheses in macros.
This was partly inspired by my wading through gcc -E output
while debugging something else, and seeing too many parens.

This patch does not change the generated .o files on my platform.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/android.c b/src/android.c
index fb7703d84ab..509f30a759b 100644
--- a/src/android.c
+++ b/src/android.c
@@ -6008,7 +6008,7 @@ android_build_jstring (const char *text)
    is created.  */
 
 #if __GNUC__ >= 3
-#define likely(cond)    __builtin_expect ((cond), 1)
+#define likely(cond)    __builtin_expect (cond, 1)
 #else /* __GNUC__ < 3 */
 #define likely(cond)    (cond)
 #endif /* __GNUC__ >= 3 */