Hi, Is this a real or potential issue? C interoperability has been implemented in all compilers I know of for a while. In 2007, cray, gfortran, g95, intel and NAG already supported this functionality. http://dx.doi.org/10.1145/1243413.1243414 The current version is at http://dx.doi.org/10.1145/2073761.2073762 (I wish it would also give the earliest release each feature was implemented). For those who don't use fortran and may not have a "recent" compiler, there is always --with-fortran=0 Blaise

Barry is looking at using this flag and reorganizing the f2003 code. [perhaps the interface functions that need this functionality won't be compiled selectively - based on this flag]

Satish

On Thu, 31 May 2012, Jed Brown wrote:

...

So how do we deal with this function not being implemented unless an F2003 compiler is used? Just #ifdef its body and produce a run-time error when an old compiler is used? Satish, are you doing this?

On Thu, May 31, 2012 at 11:36 AM, Satish Balay <[email protected]> wrote:

...

Added configure check.

http://petsc.cs.iit.edu/petsc/releases/BuildSystem-3.3/rev/a6a959d40d3d

Satish

On Thu, 31 May 2012, Jed Brown wrote:

...

And we have our first petsc-maint breakage due to this Fortran 2003 thingy.

On Thu, May 31, 2012 at 9:03 AM, Satish Balay <[email protected]> wrote:

...

This code is using "use,intrinsic :: iso_c_binding"

Isn't this a fortran 2003 thingy? Perhaps there should be a configure checks for it.

Satish

On Wed, 30 May 2012, Barry Smith wrote:

...

Blaise,

I have pushed PetscOptionsGetEnum() and PetscBagRegisterEnum()

for f90 to petsc-dev tests are in src/sys/examples/tutorials

...

Barry

-- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin