Andy Lester wrote:
I guess I don't see the need to document a standard C behavior with a macro.
If you had read all the way through the message, you would see that the biggest benefit is the ability to hang debugging hooks off the macro. We have a number of these kinds of debugging hooks throughout Parrot (src/gc/memory.c is a good example).
Allison
