[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:31 -0600

-------- Original Message --------
Subject: Re: FORTRAN XTYPE
Date: Mon, 08 May 2000 12:09:17 +0200
From: Mike Mueller <address@hidden>
Organization: UCAR/Unidata
To: John Caron <address@hidden>
References:
<address@hidden><address@hidden><address@hidden>

John,

the problem was the external name interpretation scheme of the compiler.
DF6.1 by default is case sensitive, i.e. lower case names are different
from upper case names. I was not aware of this because FORTRAN is not
case
sensitive. Since DF is tightly integrated in MS DEVEVELOPER STUDIO which
also supports C/C++, case sensitivity is of interest (multi language
programming). Changing the appropriate projects settings will fix this
problem. 

Now everything works as expected.
Thanks for your help. See below for answers to your questions.
Maybe my "case" can be of some value for future users with some "strange
behaviour of netcdf".

Mike

>what's XTYPE?

used in NetCDF User?s Guide for FORTRAN:

7.2 Create a Variable: NF_DEF_VAR
...

Usage
INTEGER FUNCTION NF_DEF_VAR(INTEGER NCID, CHARACTER*(*) NAME,
INTEGER XTYPE, INTEGER NVDIMS,
INTEGER VDIMS(*), INTEGER varid)


>> 
>> 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.
>
>you keep saying NF_STERROR, but you mean  NF_STRERROR 
>

typo in email not in code