[petsc-dev] Deprecation strategy for Enums

Fande Kong fdkong.jd at gmail.com
Tue Apr 9 12:49:33 CDT 2019

I had a fix in libmesh https://github.com/libMesh/libmesh/pull/2027/files.
Are you using the old libmesh?

 Right, definitely I would love to see we have a  deprecation strategy for
everything.  This allow us manage libmesh and moose a little bit easier.


On Tue, Apr 9, 2019 at 11:39 AM Matthew Knepley via petsc-dev <
petsc-dev at mcs.anl.gov> wrote:

> This change:
> https://bitbucket.org/petsc/petsc/commits/c0decd05c6848b80907752eef350b55c8c90e696#Linclude/petscksp.hF448
> breaks the current LibMesh, and I am assuming other things. Do we have a
> deprecation strategy for this? How about we #define that old name to the
> same value for one release? We could do this
> in 3.11.1.
>   Thanks,
>     Matt
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
> https://www.cse.buffalo.edu/~knepley/
> <http://www.cse.buffalo.edu/~knepley/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190409/862de7b7/attachment.html>

More information about the petsc-dev mailing list