Although from a Unix-standards point of view we ought to be using stderr for error messages, I don't really like seeing 4 or 8 copies of every error when it's something like the messages in examples/ex*.C that are guaranteed to be printed on all processors. Would anyone mind if I changed those to use std::cout instead of cerr? Or if I at least changed the "This example requires Blah support" messages to use cout, since those end with "return 0;" instead of "error();" anyway? --- Roy
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
