I am using it in my fork test which isn't pushed. On Wed, Nov 25, 2015 at 1:49 PM, Barret Rhoden <[email protected]> wrote: > On 2015-11-25 at 13:43 Kevin Klues <[email protected]> wrote: >> Whatever you want it to. For example: >> >> void *var = malloc(100); >> memset(var, 0, 100) >> UT_ASSERT_M("Malloc work!\n", testallzero(var), { >> free(var); >> }); >> // do something else with var now... > > Ah, so it's a cleanup before you return FALSE. though you'd never use > it afterwards, since you return right after running VA_ARGS. > > Also, it looks like no one was using it either. > > I've got a change brewing that allows "message" to be a format string. > I can either leave UT_ASSERT_M as is, or create a new UT_ASSERT that > does the format printing, but not the misc cleanup. > > Barret > > -- > You received this message because you are subscribed to the Google Groups > "Akaros" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout.
-- ~Kevin -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
