On Thu, 13 Sep 2012, Derek Gaston wrote:
> Hmmm... There was a discussion all the way back in 2008 where I was > wanting to get better error messages out of libMesh... and Roy shot > me down ;-) Vengeance is yours? Actually, point me to the 2008 thread? It's possible that I was wrong and have since learned the error of my ways. > Instead of specialized assert functions like this (have you been > spending too much time with cpp_unit?? ;-) why not just make > libmesh_assert() take a string that gets printed if the assert is > false. Basically I just don't want to type things twice. I figured adding six new macros and replacing assert(a < b->size()) with assert_less(a,b->size()) was overall terser than adding one new macro and replacing every instance of assert(a < b->size()) with assert_new(a < b->size(), "a = " << a << "\nb->size() = " << b->size()) On the other hand, I like the idea of having more flexibility too. Adding assert-with-msg and error-with-msg options in addition to the assert-with-more-autogenerated-output macros sounds nice. --- 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
