From b6ed79b71ccb3df8df05531d473ff9510cf9a39f Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Sat, 20 Jan 2024 16:52:31 -0800
Subject: 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.
---
 admin/notes/java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'admin/notes/java')

diff --git a/admin/notes/java b/admin/notes/java
index 891096cd406..e10f09f780f 100644
--- a/admin/notes/java
+++ b/admin/notes/java
@@ -445,7 +445,7 @@ loaded by the special invocation:
 where ``static'' defines a section of code which will be run upon the
 object (containing class) being loaded.  This is like:
 
-  __attribute__((constructor))
+  __attribute__ ((constructor))
 
 on systems where shared object constructors are supported.
 
-- 
cgit v1.2.1