On Fri, Dec 19, 2008 at 8:47 AM, Gennadiy Rozental <rogeeff@gmail.com> wrote:
Dean Michael Berris wrote:
I'm using Boost 1.35 and I notice that when a unit test aborts due to asserts in the code, it doesn't count as a failure -- the end report says "*** No errors detected" when in fact a call to abort() was made due to a failed assert.
I'm thinking this would be a bug, but I'd like to ask first whether this is intended behavior before thinking it's a bug with Boost.Test.
I believe this was fixed in 1.36.0
Would there be a patch that would fix this for 1.35.0? If not, where should I be looking to get this fixed in 1.35.0? Because upgrading to 1.36 (or anything higher for that matter) is not an option for me at the moment. Thanks. -- Dean Michael C. Berris Software Engineer, Friendster, Inc.