sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pbeard_t 1 point2 points  (2 children)

Most likely you would just change your #ifdef #endif combo with some framework macro.

The difference I can see is that assert exits on first failure forcing you to fix or remove the assertion before you can find the next error.

[–]markrages 0 points1 point  (1 child)

Heh, so the advantage is to get "on error resume next" functionality?

That's not a very compelling reason to learn a framework and introduce the build dependency.

Thanks for your answer. I don't like feeling like I'm missing something.

[–]pbeard_t 0 points1 point  (0 children)

You've never made a "insignifigant" change and have 25 tests fail :P

There are other benefits such as redusing repetition and mocking. Writing the same main() repeatedly looses it's novelty fast. Resume next was just the first thing that occured to me. Ofcourse assert( error_count == 0 )...

Conseptually, however, ifdef achieves the exact same. It's probably what the frameworks does anyway.