On Sat, Feb 2, 2013 at 4:00 PM, Dmitry Karpeev <karp...@mcs.anl.gov> wrote:
> I was actually considering maintaining backward-compatibility since there
> may be a small number of people (perhaps only Ata) that could be using this
> functionality, although it is still pretty new. Replacing these entirely
> with DMSNESXXX would require them to upgrade to petsc-dev or petsc-3.4
> (once it's out). I'm not yet sure what's easier overall.
Libmesh supports older versions of PETSc, so, since that's your code,
you're obligated to make it support old versions of PETSc. You may be able
to do that by disabling the functionality entirely (so libmesh builds with
an old PETSc, but those functions would fail at run-time). The decision of
_how_ (not if) to maintain backward compatibility is why I started this
thread.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel