[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

960118: NETCDF fortran errors with linux

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 960118: NETCDF fortran errors with linux
  • Date: Thu, 18 Jan 96 12:57:28 -0700
Darin,

>Date: Thu, 18 Jan 1996 14:26:51 -0500 
>From: Darin Ernst <address@hidden>
>Organization: . 
>Subject: Re: 960118: NETCDF fortran errors with linux 
>Keywords: 199601171614.AA16237

In the above message you wrote:

> I put in the {type *,'xxxx=',xxx} statements, and you are right,
> the fortran ftest.f is calling ncddef with all null arguments.
> Are these explicitly typed in the test code?

Yes.  In ftest.src (alias ftest.f) they are initialized in a FORTRAN
BLOCK DATA statement.  Your translated version appears to get the types
right, but doesn't appear to initialize them.  The function ftnblkd()
in the translated code appears to contain sufficient information to
allow another function to correctly initialize the values (providing
the variables DATAVAL and DATAVAR are global) . I would guess that the
function ftnini() should be responsible for initializing the variables.
It doesn't appear to be doing its job.

At this point, I'd be leary of all static and BLOCK DATA variable
initializations in the translated code.

> When I get a chance, I'll look further.

Please do.  And please let me know what you discover.

--------
Steve Emmerson   <address@hidden>