On Mon, 30 Jul 2012, Paul T. Bauman wrote:
> 3. I had to remove the calculate_dphi = true assignment in the > get_dphidxi, etc. calls, but I've at least left the asserts there. > The problem is that we may need dphidxi without actually needing > dphi. The only time this will break is if the user *only* calls > get_phi, but also calls get_dphidxi. Can anyone think of a case > where this would happen (I couldn't come up with one)? Sure: any application code which only uses the component arrays without using the gradient array will now be failing that assertion in debug mode or probably accessing OOB memory in opt mode. Why can't we set "calculate_dphi = true" there? I'd rather take the component arrays out entirely than leave them in there booby-trapped. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
