> Cool Ben. I think this is a good direction. You know though... we haven't > switched any of our code over to the new Object interfaces yet ;-) I'll try > to do that pretty soon so you can get some feedback on this stuff...
That's fair - in cases like this where it is easy and natural to maintain backwards compatibility there is no pressing reason to switch. I use the new interfaces though with new code I've written, and I got to a point where in Adam's ablation code we need to augment the send list and sparsity pattern for contact conduction... And I didn't want to write a new C-style function pointer and context. I agree the function pointers are quite a throwback, but they were the first user-interaction part of the API to be written. And then (as now and always...) I was just scratching the surface of the capability that is C++, so I kinda just did the first thing that worked. -Brn ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
