On Thu, 18 Oct 2012, Cody Permann wrote: > We might not be able to take a look at this until Monday, but we'll > definitely let you know.
Oh, no rush - recall that my original plan was "remove the prepare_for_use argument after a release or two". While you're looking at semi-internal APIs, though, a more urgent question: are you codes using any of the DofMap constraints generation APIs (i.e. create_dof_constraints(), process_constraints(), add_constraint_row())) in any "unexpected ways" (i.e. other than via System::init_data() via EquationSystems::reinit(), and/or within System::user_constrain())? I've found a ParallelMesh AMR bug that's not going to be fixable without at least adding an argument to DofMap::process_constraints(), and if I've got to mess with the DofMap guts anyway, I might take the opportunity to refactor things to leave those guts less exposed. --- Roy ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
