Barry,   As a regular used of PETSc in Fortran, I see no problem with these changes to the Fortran interface. -sanjay -------------------------------------------------------------------- On 6/5/24 10: 14 AM, Barry Smith wrote: I am working to
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Barry,
  As a regular used of PETSc in Fortran, I see no problem with these changes to the Fortran interface.
-sanjay
--------------------------------------------------------------------
On 6/5/24 10:14 AM, Barry Smith wrote:
I am working to improve PETSc support for Fortran and to automate more of the process so our Fortran coverage will be complete and always up-to-date. This will require a few small changes in the usage from Fortran. Could you please take a look
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd

I am working to improve PETSc support for Fortran and to automate more of the process so our Fortran coverage will be complete and always up-to-date.

This will require a few small changes in the usage from Fortran. 

Could you please take a look at https://gitlab.com/petsc/petsc/-/merge_requests/7598 and make any comments or suggestions.

Thanks

  Barry

The changes would appear in the next release of PETSc in October and would not slightly backward incompatible with older versions of PETSc. But the compiler will tell you what needs to be updated.