Asserted Macros are Expanded Before Stringification

[nemequ]

Asserted Macros are Expanded Before Stringification

[nemequ]

Maybe I'm misunderstanding the point of this report, but it seems like µnit already does what you're talking about. You've elided the portion which shows the expanded value. The full string should look something like:

assertion failed: SOME_LONG_UGLY_EXPRESSION == 7 (0 == 7)

Both versions are shown because both can be useful in different situations.

[webstrand]

I guess I should've included the message I expected:

assertion failed: FOO == 7 (0 == 7)

The problem with reporting the expansion of FOO is that a macro's expansion is often cryptic and doesn't provide any additional information. Also if the expansion contains format strings, or even sequences of characters that parse as flags, at best spurious warnings will be produces and at worst the assertion causes a segmentation fault.

If the current behavior is the desired behavior, I suppose the security issues can be fixed by passing the expansion as a parameter to printf rather than using the preprocessor to concatenate the strings.