Printable View
Hello everyone,
I can not understand how the following code works and assign 100 to counter variable?
Code:void Foo (int* input)
{
*input = 100;
return;
}
#define GETFOO (Foo( &counter ), counter)
int counter;
int main()
{
GETFOO;
return 0;
}
thanks in advance,
George
Can you clarify what you don't understand?
The assignment, to me, is quite straightforward: It passes a pointer to counter, which is then assigned 100 in the Foo function.
--
Mats
What's with the , [comma ]operator here?Code:#define GETFOO (Foo( &counter ), counter)
Rather superfluous in this context, methinks.Quote:
What's with the , [comma ]operator here?
Yes, but if you where to do something like:Quote:
Originally Posted by laserlight
it would lead to x being assigned the value of counter.Code:int x = GETFOO;
--
Mats
Yes, it would not be superfluous in such a context, but I think this whole thing is rather suspect... a code obfuscation contest?Quote:
Originally Posted by matsp
I _HAVE_ seen code that actually does this type of thing - slightly more complex in fact - but I'd rather see it implemented as an inline function if at all possible. The code where I saw it actually used some textual replacement in the macro, so a function wouldn't quite work in that case. It was kernel code, so probably not really intended for "easy readability" tho'.Quote:
Originally Posted by laserlight
--
Mats
Good lord, how many times must you spam the same question on every board you can find?
http://forums.microsoft.com/MSDN/Sho...42316&SiteID=1
http://forums.devarticles.com/c-c-he...ks-128335.html
http://www.thescripts.com/forum/thread747894.html
http://www.eggheadcafe.com/software/...cro-works.aspx
http://cboard.cprogramming.com/showthread.php?t=96874
http://www.codeguru.com/forum/showthread.php?t=441197
rdrast, George2 does that all the time, I'm getting used to it.
LaserLight, I suppose I should, but honestly... That kind of spamming inclines me to simply ignore anything I see by him, and others that do the same.
Guess I'm just in a general bad mood this day, and that set me off :)
Be well.
Ok, so perhaps we should stop answering such questions - as there's probably an equally good answer floating about somewhere else. It is really annoying when you find that someone else posted the same answer 5 hours ago, when you have spent some considerable effort to explain something [not necessarily the case in this particular thread, but...]Quote:
Originally Posted by laserlight
--
Mats