On Thu, Feb 7, 2013 at 1:17 PM, Derek Gaston <fried...@gmail.com> 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. I mean... it's
> worked this way for the last 10+ years without real complaint....
I'm afraid your workaround is really fragile and can fail in very
non-obvious ways. I may be biased, but I think communicators are
unbelievably useful.
Imagine if you couldn't have more than one file descriptor open at once. Of
course you could work around it by saving the offset and seeking on
re-open, but it would be terribly confusing and break in weird ways. FWIW,
we have quite a number of places in PETSc where we interact with more than
one non-self communicator. That stuff would be unmaintainable at best if
not for our explicit use of communicators.
------------------------------------------------------------------------------
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
