On Tue, 16 Oct 2012, Derek Gaston wrote: > Firstly, we heavily use this option - we _never_ renumber (when > possible - it's not possible with ParallelMesh for instance).
I'll take that as another vote for "don't remove the existing option until the new option has been available for a couple releases". > Secondly: Please, for the love of god, can we get rid of this being a double > negative? > I vote for: > > MeshBase::allowNodeAndElemRenumbering(bool) The reason for the double negative is to emphasize that renumbering is the default, but that's a weak reason. Unless someone else disagrees I'll change it to "allow_renumbering" or some such shortly. --- Roy ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
