Mismatch in explicit fortran interface for MatGetInfo

[Stephan Kramer]

Hi Satish,

I tried with p6 and it indeed works fine now. Thanks a lot for looking 
into this. A related question: it seems still quite a lot of very common 
interfaces (PETScInitialize, KSPSettype, MatView, etc.) are missing. Are 
there any plans of adding those in the future?

Cheers
Stephan

Satish Balay wrote:
> On Sat, 30 May 2009, Stephan Kramer wrote:
> 
>> Satish Balay wrote:
>>> On Sat, 30 May 2009, Stephan Kramer wrote:
>>>
>>>> Thanks a lot for looking into this. The explicit fortran interfaces are in
>>>> general very useful. The problem occurred for me with petsc-3.0.0-p1. I'm
>>>> happy to try it out with a more recent patch-level or with petsc-dev.
>>> Did you configure with '--with-fortran-interfaces=1' or are you
>>> directly using '#include "finclude/ftn-auto/petscmat.h90"'?
>>>
>> Configured with '--with-fortran-interfaces=1', yes, and then using them via
>> the fortran modules: "use petscksp", "use petscmat", etc.
> 
> ok. --with-fortran-interfaces was broken in p0, worked in p1,p2,p3,p4
> - broken in curent p5. The next patch update - p6 will have the fix
> for this issue [along with the fix for MatGetInfo() interface]
> 
> Satish
>