On 1 August 2017 at 11:22, Lisandro Dalcin <[email protected]> wrote: > On 31 July 2017 at 19:47, Barry Smith <[email protected]> wrote: >> >>> On Jul 31, 2017, at 4:40 AM, Lisandro Dalcin <[email protected]> wrote: >>> >>> What's the proper way of handling this? What would happens if someone >>> builds with CFLAGS=-Werror ? Should I write a ftn-custom wrapper by >>> hand to avoid potential issues? Maybe the fortran wrapper generation >>> infrastructure should re-define the PETSC_DEPRECATED macro to empty? >> >> Can it be redefined in petsc/private/fortranimpl.h which is included for >> all Fortran stub generation? >> > > Yes, that should work. > > However, I have an additional question: How are Fortran users supposed > to be notified about the deprecation? >
Additional note: It seems to me that all these deprecated routines implemented with PETSC_STATIC_INLINE in header files will not show up in the Fortran wrappers, so the deprecation is just for C/C++, in Fortran is actually a removal. -- Lisandro Dalcin ============ Research Scientist Computer, Electrical and Mathematical Sciences & Engineering (CEMSE) Extreme Computing Research Center (ECRC) King Abdullah University of Science and Technology (KAUST) http://ecrc.kaust.edu.sa/ 4700 King Abdullah University of Science and Technology al-Khawarizmi Bldg (Bldg 1), Office # 0109 Thuwal 23955-6900, Kingdom of Saudi Arabia http://www.kaust.edu.sa Office Phone: +966 12 808-0459
