On Mon, 14 Mar 2016, John Peterson wrote: > --separate-libmeshout --redirect-stdout > > Then libMesh::out gets redirected to files, and std::cout would remain > untouched, so you could work with some other app that modified it, or use > it to keep printing to the screen? I'm not sure if that's very compelling, > but I can't think of any other big use cases.
Redirecting to file is more of a use case for libMesh::err, which can otherwise be unintelligible when lots of different processes are trying to use it at once. With libMesh::out IMHO the other justification is it lets us be a good low-level library (by not touching output streams if the calling program doesn't want us to; not even shutting down cout on other ranks) while still doing our default chatty/verbose thing for typical use cases. --- Roy ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users