On Mon, 19 Jan 2009, Derek Gaston wrote:

> Or... you could use libMesh SVN.  In general this isn't a bad idea.  Most 
> development activities in libMesh tend not to impact "normal" users on a day 
> to day basis.

This is typically true - even when utterly upending the mesh class
hierarchy to add some parallel meshing support, we managed to keep the
required user application changes down to literally "replace Mesh with
MeshBase in one or two lines of code".

> Note all of the qualifiers in those sentences... just to cover my butt.

In about 5 minutes I plan to make the SVN commit I warned about
Friday.  Although not affecting the core APIs, the change will break
every application using FEMSystem, and will probably require dozens to
hundreds of lines of (mostly straightforward) changes to fix those
applications.

So, yeah, nice timing with the qualifiers.

For anyone who's worked on an FEMSystem app with me: I'll be
committing compatibility changes to the stuff in the CFDLab SVN
shortly after I change the library.  For anyone who's working on their
own FEMSystem stuff and who's just been horribly inconvenienced: email
me and I can send a perl script to make 90% of the updates your app
will need automatically.
---
Roy

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to