Outliner: distinguish non-active refs from broken refs

[lyx.git] / src / support / lassert.h

diff --git a/src/support/lassert.h b/src/support/lassert.h
index f9328f3581e97e322e017746535ef61f502873cb..b142cc2f59de5709d32a906c096107d609686384 100644 (file)
--- a/src/support/lassert.h
+++ b/src/support/lassert.h
@@ -31,15 +31,15 @@ LATTEST(expr)
   This macro should be used when one just wants to test expr. If devel mode,
   this will lead to an assertion. In release mode, we will simply continue. So
   LATTEST should be used only if you know, in advance, that it will be safe to
-  continue with the usual program flow, but failure of expr still means that 
+  continue with the usual program flow, but failure of expr still means that
   there is something that needs to be fixed.
 
 LASSERT(expr, escape)
-  This macro should be used when a failure of expr is not compatible with 
+  This macro should be used when a failure of expr is not compatible with
   continuing the ordinary program flow, but is something from which we can
   recover. This might mean simply returning early from some routine; it might
   mean resetting some variables to values known to be sane; it might mean
-  taking some other corrective action. 
+  taking some other corrective action.
 
 LWARNIF(expr)
   This macro should be used when a failure of expr indicates that the current
@@ -56,7 +56,7 @@ LAPPERR(expr)
   This macro should be used if a failure of expr is incompatible with LyX
        continuing to operate at all. In release mode, this issues an ErrorException,
   which typically results in an emergency shutdown.
-       
+
 ******************************************************************************/
 
 
@@ -65,6 +65,8 @@ void doWarnIf(char const * expr, char const * file, long line);
 void doBufErr(char const * expr, char const * file, long line);
 void doAppErr(char const * expr, char const * file, long line);
 
+void doAssertWithCallstack(bool value);
+
 /// Print demangled callstack to stderr
 docstring printCallStack();