On Thu, 20 Sep 2012, Paul T. Bauman wrote:
2. Put accessors around the raw member variables. Hopefully then
future changes would be less likely to cause API breakage.
I'm, say, 30% of the way through this already (from FEAbstract work, etc.);
there was a devel thread on this - I'm not going rogue! Should I/we
try to finish before the next release?
I'm actually hoping we could get one more release out first - we've
already had a little backwards compatibility breakage with the
"periodic_boundary.h" creation, and I like to only torture our users a
little at a time.
On the other hand there's something to be said for letting them
immediately edit code to match a stable release...
Okay, here's the nicest thing to do: the next release should have the
accessors available, but we shouldn't make the underlying data members
private until immediately after the release.
I'm all for better intuitive naming.
Any preferences on residual/jacobian vs rhs/matrix?
---
Roy
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
