Mercurial > hg > octave-nkf

diff liboctave/util/oct-locbuf.cc @ 19607:95c533ed464b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
use warning IDs for all warnings in liboctave * CSparse.cc, MatrixType.cc, Sparse.cc, dSparse.cc, dbleQR.cc, eigs-base.cc, lo-specfun.cc, cmd-hist.cc, data-conv.cc, kpse.cc, lo-regexp.cc, oct-locbuf.cc, oct-shlib.cc, sparse-util.cc: Use current_liboctave_warning_with_id_handler and provide warning IDs for all warnings in liboctave code. * unwinddemo.cc: Also preserve and restore warning_wit_id_handler.
author John W. Eaton <jwe@octave.org>
date Thu, 18 Dec 2014 10:50:09 -0500
parents 49a5a4be04a1
children 4197fc428c7d
line wrap: on
line diff
--- a/liboctave/util/oct-locbuf.cc
+++ b/liboctave/util/oct-locbuf.cc
@@ -140,8 +140,12 @@
     }
   else
     {
-      (*current_liboctave_warning_handler)
-        ("octave_chunk_buffer::clear: %d active allocations remain!",
+      // FIXME: Doesn't this situation represent a programming error of
+      // some kind?  If so, maybe this should be a fatal error?
+
+      (*current_liboctave_warning_with_id_handler)
+        ("Octave:local-buffer-inconsistency",
+         "octave_chunk_buffer::clear: %d active allocations remain!",
          active);
     }
 }