On Wed, 20 Aug 2008, Derek Gaston wrote:
> For now, I do think I'll add another constructor for NotImplemented
> that takes a string so that you can do:
>
> LIBMESH_THROW(libMesh::NotImplemented("Something::somehwere()");
I don't like that; in theory we can get at least that much info
automatically (minus transposition typos ;-) ) from the same stack
inspection + demangling calls that we use for tracefiles, and on other
systems we can at least get filename and line number automatically.
> If you come up with this Macro... just let me know what it is and I'll
> start using it!
libmesh_not_implemented();
It'll just do the same output as libmesh_error() (except for
mentioning "not implemented" instead of "logic error") for now, but
that'll at least allow looking at tracefiles or looking up file/line
numbers in source code to find the function name.
---
Roy
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
