On Mon, 15 Aug 2016, Kirk, Benjamin (JSC-EG311) wrote:
Might be a slight complication for unit testing but that's no reason not to do
the right thing...
On Aug 15, 2016, at 12:01 PM, John Peterson <jwpeter...@gmail.com> wrote:
> Sounds reasonable to me. The only reason off the top of my head
> would be if it was a common pattern for one to build/manage
> DofMaps manually, but this definitely is not the case AFAIK.
Okay, thanks; I'll make the change along with my next PR.
I just now noticed the last straw: DofMap::_sys_number. So not only
would a single DofMap only be useful on two meshes if they were
identical, it would only be shareable between two systems with the
same number.
One of these days I imagine tearing through libMesh and changing APIs
to turn as many internal two-way dependencies into one-way
dependencies as possible, but that day is not today.
---
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
