On Mar 11, 2010, at 11:27 AM, John Peterson wrote: > On Thu, Mar 11, 2010 at 12:23 PM, Roy Stogner <[email protected]> > wrote: >> >> E. Making libMesh::out a class which internally stores an ostream*, >> and which has a "reset(ostream&)" function to change it, a templated >> operator<< method to pass output to it, and an implicit >> conversion-to-ostream& operator to return it. This is the prettiest >> thing to do for user code, since then "libMesh::out << whatever" works >> and users can mostly treat it as they would a std::ostream, but I was >> wary that I might be forgetting about exceptions (in the metaphorical >> sense, but maybe also in the literal?). > > This.
Seconded. If the class gets really fancy it can even handle the "packetized" sending of output info to processor 0 Roy was talking about. Derek ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
