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

[Fwd: Re: FORTRAN XTYPE]

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: [Fwd: Re: FORTRAN XTYPE]
  • Date: Mon, 08 May 2000 13:44:13 -0600

-------- Original Message --------
Subject: Re: FORTRAN XTYPE
Date: Fri, 05 May 2000 18:33:48 +0200
From: Mike Mueller <address@hidden>
Organization: UCAR/Unidata
To: John Caron <address@hidden>
References:
<address@hidden><address@hidden>

John,

thanks for your fast reply.
I solved the problem with XTYPE. 
It was a problem with the INCLUDE of netcdf.inc.

At 10:05 05.05.00 -0600, you wrote:
>How did you get around your NF_STRERROR problem?

Have not solved the problem yet. Just don't use NF_STERROR.
Have to look up the corresponding error number in netcdf.inc.

>Mike Mueller wrote:
>> 
>> I am using netCDF3.5 under WIn NT and DF 6.1
>> All external datatypes are 0 even so I included netdf.inc.
>
>What do you mean "all are 0"?
>
WRITE(*,*) NF_DOUBLE
output on screen  0
got this one (see above).

Thanks 
Mike