To use the latest version of PETSc, each user needs to remove the error 
checks on these calls. The resulting code will work with previous versions of 
PETSc as well as the current version of PETSc.  PETSc has never promised 
complete backward compatibility in the sense of promising that one can use new 
PETSc releases without any changes to their code; the documentation has always 
stated new releases will contain changes in the API. We began using depreciate 
a few years ago to limit the number of changes that needed to be made 
immediately for each release but depreciate is not suitable for all changes and 
so users do need to make some changes for each new release. 

   



> On Apr 3, 2022, at 7:23 AM, Lisandro Dalcin <dalc...@gmail.com> wrote:
> 
> The recent PetscUse/TryMethod changes are backward incompatible. Third-party 
> codes cannot compile without modification. Our users deserve better.
> 
> 
> -- 
> Lisandro Dalcin
> ============
> Senior Research Scientist
> Extreme Computing Research Center (ECRC)
> King Abdullah University of Science and Technology (KAUST)
> http://ecrc.kaust.edu.sa/ <http://ecrc.kaust.edu.sa/>

Reply via email to