Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

77%
+5 −0
Q&A When should I parenthesize macro arguments in C?

I've seen macros use parentheses to enclose its arguments. Most of these make sense, as in #define sum(a, b) ((a) + (b)) The outer prevents the following: #define sum_bad(a, b) (a) + (b) ...

2 answers  ·  posted 12mo ago by alx‭  ·  last activity 12mo ago by Lundin‭

Question c macros
#4: Post edited by user avatar alx‭ · 2023-11-12T11:46:11Z (12 months ago)
  • When should I parenthesize my macro arguments in C?
  • When should I parenthesize macro arguments in C?
#3: Post edited by user avatar alx‭ · 2023-11-11T19:22:57Z (12 months ago)
  • I've seen macros use parentheses to enclose its arguments. Most of these make sense, as in
  • ```c
  • #define sum(a, b) ((a) + (b))
  • ```
  • The outer prevents the following:
  • ```c
  • #define sum_bad(a, b) (a) + (b)
  • s = sum_bad(x, y) * z; // (x) + (y) * z
  • ```
  • The inner prevents the following:
  • ```c
  • #define mul_bad(a, b) (a * b)
  • m = mul_bad(x, y + z); // (x * y + z)
  • ```
  • ----
  • However, I've seen some parentheses that don't seem justified.
  • ```c
  • #define foo(a, b) bar((a), (b)) // Why not just `bar(a, b)`
  • ```
  • ```c
  • #define asd(a, b) do \
  • {
  • int x = (b); // Why not just `= b;`?
  • zxc(x);
  • }
  • ```
  • Is it really necessary to always enclose macro arguments in parentheses, or is it superfluous in some cases?
  • I've seen macros use parentheses to enclose its arguments. Most of these make sense, as in
  • ```c
  • #define sum(a, b) ((a) + (b))
  • ```
  • The outer prevents the following:
  • ```c
  • #define sum_bad(a, b) (a) + (b)
  • s = sum_bad(x, y) * z; // (x) + (y) * z
  • ```
  • The inner prevents the following:
  • ```c
  • #define mul_bad(a, b) (a * b)
  • m = mul_bad(x, y + z); // (x * y + z)
  • ```
  • ----
  • However, I've seen some parentheses that don't seem justified.
  • ```c
  • #define foo(a, b) bar((a), (b)) // Why not just `bar(a, b)`
  • ```
  • ```c
  • #define asd(a, b) do \
  • {
  • int x = (b); // Why not just `= b;`?
  • zxc(x);
  • } while (0)
  • ```
  • Is it really necessary to always enclose macro arguments in parentheses, or is it superfluous in some cases?
#2: Post edited by user avatar alx‭ · 2023-11-11T06:05:09Z (12 months ago)
  • I've seen macros use parentheses to enclose its arguments. Most of these make sense, as in
  • ```c
  • #define sum(a, b) ((a) + (b))
  • ```
  • The outer prevent the following:
  • ```c
  • #define sum_bad(a, b) (a) + (b)
  • s = sum_bad(x, y) * z; // (x) + (y) * z
  • ```
  • The inner prevents the following:
  • ```c
  • #define mul_bad(a, b) (a * b)
  • m = mul_bad(x, y + z); // (x * y + z)
  • ```
  • ----
  • However, I've seen some parentheses that don't seem justified.
  • ```c
  • #define foo(a, b) bar((a), (b)) // Why not just `bar(a, b)`
  • ```
  • ```c
  • #define asd(a, b) do \
  • {
  • int x = (b); // Why not just `= b;`?
  • zxc(x);
  • }
  • ```
  • Is it really necessary to always enclose macro arguments in parentheses, or is it superfluous in some cases?
  • I've seen macros use parentheses to enclose its arguments. Most of these make sense, as in
  • ```c
  • #define sum(a, b) ((a) + (b))
  • ```
  • The outer prevents the following:
  • ```c
  • #define sum_bad(a, b) (a) + (b)
  • s = sum_bad(x, y) * z; // (x) + (y) * z
  • ```
  • The inner prevents the following:
  • ```c
  • #define mul_bad(a, b) (a * b)
  • m = mul_bad(x, y + z); // (x * y + z)
  • ```
  • ----
  • However, I've seen some parentheses that don't seem justified.
  • ```c
  • #define foo(a, b) bar((a), (b)) // Why not just `bar(a, b)`
  • ```
  • ```c
  • #define asd(a, b) do \
  • {
  • int x = (b); // Why not just `= b;`?
  • zxc(x);
  • }
  • ```
  • Is it really necessary to always enclose macro arguments in parentheses, or is it superfluous in some cases?
#1: Initial revision by user avatar alx‭ · 2023-11-10T23:47:04Z (12 months ago)
When should I parenthesize my macro arguments in C?
I've seen macros use parentheses to enclose its arguments.  Most of these make sense, as in

```c
#define sum(a, b)  ((a) + (b))
```

The outer prevent the following:

```c
#define sum_bad(a, b)  (a) + (b)

s = sum_bad(x, y) * z;  // (x) + (y) * z
```

The inner prevents the following:

```c
#define mul_bad(a, b)  (a * b)

m = mul_bad(x, y + z);  // (x * y + z)
```

----

However, I've seen some parentheses that don't seem justified.

```c
#define foo(a, b)  bar((a), (b))  // Why not just `bar(a, b)`
```

```c
#define asd(a, b)  do \
{
    int x = (b);  // Why not just `= b;`?

    zxc(x);
}
```

Is it really necessary to always enclose macro arguments in parentheses, or is it superfluous in some cases?