Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 10/31/2011 03:31 PM, Terrence Enger wrote:
There has been a lot of discussion in the past about raised
assertions and how seriously they should be treated.  Is
there a current concensus?

I raise the question again for no better reason than that
even a newbie like me can see a raised assertion and collect
a backtrace.  Guidance welcome.

OOo earlier this year introduced a mechanism to let smoketestoo_native fail in case of assertions (implemented by somebody who did not come from the "assertions need to abort. period." camp, btw). LibO promptly imported that feature (without any debate AFAIK).

For me at least, this implies that all occurrences of firing assertions should be tracked and fixed.

(For me at least, this also implies that assertions---OSL_ASSERT, OSL_ENSURE, OSL_FAIL, DBG_ASSERT---should only be used to flag illegal program states, not for unexpected but legal ones. I don't think there is objection to this view in general. I've only seen confusion about which macro was designed for which use case, and a sort of indifference a la "half of the time, OSL_ASSERT etc. are used with the wrong semantics anyway; shrug.")

Stephan

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.