I'll put together a "FakeCommunicator" class implementation sometime today or
tonight, then, and we can try it out. The stack trace should work just fine.
We do want Mesh(CommWorld) to fail in the --disable-default-comm case, and we
also want Mesh() to fail... but we want *some* way to create a mesh without
failing. My proposal was "Mesh(libmeshinit.communicator());" Expresses what
we'd want to do when creating a mesh in main(), but because LibMeshInit objects
usually aren't in scope anywhere else it'd be hard for app codes to "abuse" and
thereby inadvertently make themselves less extensible to the multi-communicator
case.
---
Reply to this email directly or view it on GitHub:
https://github.com/libMesh/libmesh/issues/71#issuecomment-15906296
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
