summaryrefslogtreecommitdiff
path: root/admin
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2024-01-20 16:52:31 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2024-01-20 17:28:53 -0800
commitb6ed79b71ccb3df8df05531d473ff9510cf9a39f (patch)
treecea1f448b8e163fc0972b09774f075f9c2277372 /admin
parent0a47a5a4bef0a33c012302346685ecab861cc306 (diff)
downloademacs-b6ed79b71ccb3df8df05531d473ff9510cf9a39f.tar.gz
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.
Diffstat (limited to 'admin')
-rw-r--r--admin/notes/java2
1 files changed, 1 insertions, 1 deletions
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.