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


On 30/11/12 15:19, Maciej Rumianowski wrote:
Hi Bjoern,

thanks for reply :)

    So, to change the conditionals, we need to make sure the state is
    consistent.
    Thus:
    - adding the asserts

Do you mean  DBG_ASSERT or real assert?

if the goal is to track down client code that is making erroneous calls
to an internal interface, assert() is clearly the way to go: it will
abort the program when built in any debug mode (e.g. --enable-debug or
--enable-dbgutil) and makes any unit test that triggers such an
erroneous call fail, which is what you want to track those down.

DBG_ASSERT is only active with --enable-dbgutil, and just prints a
message that is easily ignored.

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.