On Mon, Mar 14, 2016 at 10:30 AM, David Knezevic <[email protected] > wrote:
> I was just wondering if someone could explain the reasoning behind why we > have libMesh::out and how it differs from std::cout? I guess the idea is > that libMesh::out defaults to std::cout, but that we can change it to > something else if we want to? Are there any examples of when it would make > sense to define libMesh::out to something other than std::cout? > I think if you say: --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. -- John ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
