Variables C macro function
up vote
0
down vote
favorite
What's happening in this macro? I understand that #test expand this parameter to the literal text. But what does pre;
and test;
do?
#define MACRO_FN(test, pre, repeat, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
This is used like so
MACRO_FN(a_func(an_array, size),, var1, size);
What do the double commas mean here?
c macros c-preprocessor
|
show 5 more comments
up vote
0
down vote
favorite
What's happening in this macro? I understand that #test expand this parameter to the literal text. But what does pre;
and test;
do?
#define MACRO_FN(test, pre, repeat, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
This is used like so
MACRO_FN(a_func(an_array, size),, var1, size);
What do the double commas mean here?
c macros c-preprocessor
3
Run the code through the preprocessor and look what the macro expands to.
– Some programmer dude
Nov 19 at 12:36
1
To omitpre;
- maybe? Did you check the pre-processed code?
– Sourav Ghosh
Nov 19 at 12:37
I didn't think to check the output of the pre-processor, but I'll do that now
– Jack Evans
Nov 19 at 12:47
2
When invoking a preprocessor macro , "blank" is a valid argument; the callMACRO_FN(a,,b,c)
means thatpre
will expand to blank
– M.M
Nov 19 at 12:50
2
Please note that macros like these should be avoided like the plague.
– Lundin
Nov 19 at 12:55
|
show 5 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
What's happening in this macro? I understand that #test expand this parameter to the literal text. But what does pre;
and test;
do?
#define MACRO_FN(test, pre, repeat, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
This is used like so
MACRO_FN(a_func(an_array, size),, var1, size);
What do the double commas mean here?
c macros c-preprocessor
What's happening in this macro? I understand that #test expand this parameter to the literal text. But what does pre;
and test;
do?
#define MACRO_FN(test, pre, repeat, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
This is used like so
MACRO_FN(a_func(an_array, size),, var1, size);
What do the double commas mean here?
c macros c-preprocessor
c macros c-preprocessor
edited Nov 19 at 14:15
asked Nov 19 at 12:34
Jack Evans
385
385
3
Run the code through the preprocessor and look what the macro expands to.
– Some programmer dude
Nov 19 at 12:36
1
To omitpre;
- maybe? Did you check the pre-processed code?
– Sourav Ghosh
Nov 19 at 12:37
I didn't think to check the output of the pre-processor, but I'll do that now
– Jack Evans
Nov 19 at 12:47
2
When invoking a preprocessor macro , "blank" is a valid argument; the callMACRO_FN(a,,b,c)
means thatpre
will expand to blank
– M.M
Nov 19 at 12:50
2
Please note that macros like these should be avoided like the plague.
– Lundin
Nov 19 at 12:55
|
show 5 more comments
3
Run the code through the preprocessor and look what the macro expands to.
– Some programmer dude
Nov 19 at 12:36
1
To omitpre;
- maybe? Did you check the pre-processed code?
– Sourav Ghosh
Nov 19 at 12:37
I didn't think to check the output of the pre-processor, but I'll do that now
– Jack Evans
Nov 19 at 12:47
2
When invoking a preprocessor macro , "blank" is a valid argument; the callMACRO_FN(a,,b,c)
means thatpre
will expand to blank
– M.M
Nov 19 at 12:50
2
Please note that macros like these should be avoided like the plague.
– Lundin
Nov 19 at 12:55
3
3
Run the code through the preprocessor and look what the macro expands to.
– Some programmer dude
Nov 19 at 12:36
Run the code through the preprocessor and look what the macro expands to.
– Some programmer dude
Nov 19 at 12:36
1
1
To omit
pre;
- maybe? Did you check the pre-processed code?– Sourav Ghosh
Nov 19 at 12:37
To omit
pre;
- maybe? Did you check the pre-processed code?– Sourav Ghosh
Nov 19 at 12:37
I didn't think to check the output of the pre-processor, but I'll do that now
– Jack Evans
Nov 19 at 12:47
I didn't think to check the output of the pre-processor, but I'll do that now
– Jack Evans
Nov 19 at 12:47
2
2
When invoking a preprocessor macro , "blank" is a valid argument; the call
MACRO_FN(a,,b,c)
means that pre
will expand to blank– M.M
Nov 19 at 12:50
When invoking a preprocessor macro , "blank" is a valid argument; the call
MACRO_FN(a,,b,c)
means that pre
will expand to blank– M.M
Nov 19 at 12:50
2
2
Please note that macros like these should be avoided like the plague.
– Lundin
Nov 19 at 12:55
Please note that macros like these should be avoided like the plague.
– Lundin
Nov 19 at 12:55
|
show 5 more comments
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Here is a minimal example:
#define repeat 5 // I added this, because 'repeat' is not mentionned in your question
#define MACRO_FN(test, pre, var1, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
void foo()
{
}
void func(int a, int b)
{
}
int main()
{
MACRO_FN(func(2, 3), foo(), var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
foo();
func(2, 3);
}
}
So that macro is a wrapper that prints the function name plus it's parameters as it is invoked with the macro and executes that function specified in the first parameter repeat
times (whatever repeat
is). If the second parameter is omitted, the function that has that name is simple not invoked before the function mentioned before as in the following example:
int main()
{
MACRO_FN(func(2, 3),, var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
;
func(2, 3);
}
}
Note:
I removed the do while(0)
from the equivalent programs for brevity, read this SO article for more information:
add a comment |
up vote
3
down vote
pre
and test
seem to be two functions.
Based on how it is written, we can guess that pre
is a function called before the test
.
The double comma has no special meaning. It is just here because the second parameter (pre
) was omitted.
Edit: As a side note that kind of macro "should be avoided like plague", as @Lundin put it.
New contributor
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Here is a minimal example:
#define repeat 5 // I added this, because 'repeat' is not mentionned in your question
#define MACRO_FN(test, pre, var1, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
void foo()
{
}
void func(int a, int b)
{
}
int main()
{
MACRO_FN(func(2, 3), foo(), var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
foo();
func(2, 3);
}
}
So that macro is a wrapper that prints the function name plus it's parameters as it is invoked with the macro and executes that function specified in the first parameter repeat
times (whatever repeat
is). If the second parameter is omitted, the function that has that name is simple not invoked before the function mentioned before as in the following example:
int main()
{
MACRO_FN(func(2, 3),, var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
;
func(2, 3);
}
}
Note:
I removed the do while(0)
from the equivalent programs for brevity, read this SO article for more information:
add a comment |
up vote
3
down vote
accepted
Here is a minimal example:
#define repeat 5 // I added this, because 'repeat' is not mentionned in your question
#define MACRO_FN(test, pre, var1, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
void foo()
{
}
void func(int a, int b)
{
}
int main()
{
MACRO_FN(func(2, 3), foo(), var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
foo();
func(2, 3);
}
}
So that macro is a wrapper that prints the function name plus it's parameters as it is invoked with the macro and executes that function specified in the first parameter repeat
times (whatever repeat
is). If the second parameter is omitted, the function that has that name is simple not invoked before the function mentioned before as in the following example:
int main()
{
MACRO_FN(func(2, 3),, var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
;
func(2, 3);
}
}
Note:
I removed the do while(0)
from the equivalent programs for brevity, read this SO article for more information:
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Here is a minimal example:
#define repeat 5 // I added this, because 'repeat' is not mentionned in your question
#define MACRO_FN(test, pre, var1, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
void foo()
{
}
void func(int a, int b)
{
}
int main()
{
MACRO_FN(func(2, 3), foo(), var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
foo();
func(2, 3);
}
}
So that macro is a wrapper that prints the function name plus it's parameters as it is invoked with the macro and executes that function specified in the first parameter repeat
times (whatever repeat
is). If the second parameter is omitted, the function that has that name is simple not invoked before the function mentioned before as in the following example:
int main()
{
MACRO_FN(func(2, 3),, var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
;
func(2, 3);
}
}
Note:
I removed the do while(0)
from the equivalent programs for brevity, read this SO article for more information:
Here is a minimal example:
#define repeat 5 // I added this, because 'repeat' is not mentionned in your question
#define MACRO_FN(test, pre, var1, size)
do {
printf("%s: ", #test);
for (int i = 0; i < repeat; i++) {
pre;
test;
}
} while (0)
void foo()
{
}
void func(int a, int b)
{
}
int main()
{
MACRO_FN(func(2, 3), foo(), var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
foo();
func(2, 3);
}
}
So that macro is a wrapper that prints the function name plus it's parameters as it is invoked with the macro and executes that function specified in the first parameter repeat
times (whatever repeat
is). If the second parameter is omitted, the function that has that name is simple not invoked before the function mentioned before as in the following example:
int main()
{
MACRO_FN(func(2, 3),, var1, size);
}
Once preprocessed, the code is equivalent to this:
int main()
{
printf("%s: ", "func(2,3)");
for (int i = 0; i < 5; i++)
{
;
func(2, 3);
}
}
Note:
I removed the do while(0)
from the equivalent programs for brevity, read this SO article for more information:
edited Nov 19 at 15:47
answered Nov 19 at 14:11
Jabberwocky
26.2k93769
26.2k93769
add a comment |
add a comment |
up vote
3
down vote
pre
and test
seem to be two functions.
Based on how it is written, we can guess that pre
is a function called before the test
.
The double comma has no special meaning. It is just here because the second parameter (pre
) was omitted.
Edit: As a side note that kind of macro "should be avoided like plague", as @Lundin put it.
New contributor
add a comment |
up vote
3
down vote
pre
and test
seem to be two functions.
Based on how it is written, we can guess that pre
is a function called before the test
.
The double comma has no special meaning. It is just here because the second parameter (pre
) was omitted.
Edit: As a side note that kind of macro "should be avoided like plague", as @Lundin put it.
New contributor
add a comment |
up vote
3
down vote
up vote
3
down vote
pre
and test
seem to be two functions.
Based on how it is written, we can guess that pre
is a function called before the test
.
The double comma has no special meaning. It is just here because the second parameter (pre
) was omitted.
Edit: As a side note that kind of macro "should be avoided like plague", as @Lundin put it.
New contributor
pre
and test
seem to be two functions.
Based on how it is written, we can guess that pre
is a function called before the test
.
The double comma has no special meaning. It is just here because the second parameter (pre
) was omitted.
Edit: As a side note that kind of macro "should be avoided like plague", as @Lundin put it.
New contributor
edited Nov 19 at 13:22
New contributor
answered Nov 19 at 12:42
Xaxetrov
464
464
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374784%2fvariables-c-macro-function%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Run the code through the preprocessor and look what the macro expands to.
– Some programmer dude
Nov 19 at 12:36
1
To omit
pre;
- maybe? Did you check the pre-processed code?– Sourav Ghosh
Nov 19 at 12:37
I didn't think to check the output of the pre-processor, but I'll do that now
– Jack Evans
Nov 19 at 12:47
2
When invoking a preprocessor macro , "blank" is a valid argument; the call
MACRO_FN(a,,b,c)
means thatpre
will expand to blank– M.M
Nov 19 at 12:50
2
Please note that macros like these should be avoided like the plague.
– Lundin
Nov 19 at 12:55