On Thu, 7 Feb 2013, Derek Gaston wrote: > I'm honestly not sure if it's worth bastardizing the rest of the > libMesh interface to handle this one case when it can be handled > pretty simply by just providing a libMesh::swap_communicator() > function.
It's not so much "this one case" as "a bunch of similar hierarchical cases". I want to be able to create multiple simultaneously-existing LibMeshInit objects when doing UQ stuff, have Systems/NumericVectors/etc that discretize within individual elements for GFEM stuff, lots of cases like that where trying to keep a global variable in the proper state is just ugly. None of that's urgent, though, so if the swapping is working for you then I won't futz with the APIs to handle the more general cases for a long time. --- Roy ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
