Re: [petsc-dev] What needs to be done before a release?
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
participants (1)
-
Satish Balay