On Mon, 18 Jul 2016, John Peterson wrote:
I can fix this. The zero determinant asserts could be changed to
libmesh_error()'s (or explicit exception throws)
libmesh_assert and kin do throw an exception, but yeah, we probably
need to change this just to get rid of the text that gets spewed to
cerr before the throw.
I wish there was a way to spew out text if-and-only-if the exception
wouldn't be caught... We could at least stick a string into the
exception object itself, for what() to report?
and then we could catch the exception in inverse_map(). It should
be an "exceptional" case, so it seems reasonable to me.
Sounds good.
Other options would be to return an error code, or pass an extra
flag to TypeTensor::solve()? In these cases you'd have to check the
flag every time...
I'd imagined an extra optional flag, but no, the exception idea is
much better.
---
Roy
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
