On Fri, 2011-11-18 at 15:25 +0100, Stephan Bergmann wrote:
Alright, so we end up with
use assert if you want an assert
SAL_WARN if you want to warn about something odd, but which isn't
necessarily definitely wrong
SAL_INFO for verbose logging
Practical question though, is on windows where does the output go ?
Should we write off all the DBG_ASSERTs as hopeless to unwind and mass
convert them all to SAL_WARNs ?
How do we feel about code that does e.g.
assert(pFoo);
if (!pFoo)
throw catchAbleFoo("wtf");
i.e. do we have a philosophical problem with gracefully/semi-gracefully
handing should-be impossible cases ?
C.
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.