On Fri, 18 May 2012, Roy Stogner wrote: > Would it make sense to have a few variant macros for common assertion > cases, so that when those (debug+devel-mode) assertions get tripped we > can immediately print more information about the failure? > > E.g. whereas > libmesh_assert(a < b); > fails with an error message like > Assertion `a < b' failed > the variant > libmesh_assert_less(a,b); > could fail with an error message like > Assertion `a < b' failed: `a' = 3, `b' = 2
This is now done, but needless to say the diff which actually converts assertions to use the more detailed macros is huge. I'm posting it to http://users.ices.utexas.edu/~roystgnr/asserts_patch for now; hopefully it can get some wider testing before going into trunk, especially considering it's about 10% hand-edited and 90% regex'ed. This may also be the last straw for me to create a "testing" branch. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
