We take MeshBase& as a necessary argument for half a dozen functions, we're going to need a MeshBase for the new ghosting functor APIs too...
Plus, we're not actually capable of handling multiple mesh objects from the same DofMap except in the case where those meshes are basically identical: we can attach SparseMatrix objects and sparsity + send_list augmentation objects that are ridiculously mesh-dependent. So is there any reason we shouldn't just bite the bullet, give the DofMap a MeshBase& at construction time, and deprecate that argument in the methods which use it? --- Roy ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
