Some static analysis tools pointed me to a few problems with the Elem::SideIter class - basically there's a correctness mistake that's masked by a performance mistake.
This is fixable, but this is also code that I find literally no usage of in the rest of the library or our example apps. I'm not sure what's the better option: fix the SideIter code, or simplify the API by deprecating the SideIter code now and removing it eventually? --- Roy ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
