Scoping macros in C/C++

[tt_su]

Continuing the discussion from Heap Corruption with the SDK - How to resolve?:

@hgschutte1

The do {} while(0) is literally nothing more than habit: I tend to add that in all of my macro “functions” to eliminate scoping issues and keep things contained. The only exception to this rule is with one liners and such. It’s not an uncommon practice - actually highly recommended

Isn’t simple {} brackets enough to create a new scope?

[bugra]

It’s an old trick. A simple {} causes code style issues sometimes. Explained here:

C multi-line macro: do/while(0) vs scope block

I don’t really use the do-while style and it’s best to try to avoid macros altogether IMHO. Sometimes they are unavoidable though.

[hgschutte1]

I agree: macros can be a pain to debug as well. I think they really shine for certain forms of error checking, though. With OpenGL, especially, I’m finding that approach near necessary.

Still, in this case one could define a function which simply takes SUResult as a param and perform the check that way (though early-outs would be lost in return).