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

Re: 971209: Netcdf 3.3.1 and support for the 2.* interface

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: Re: 971209: Netcdf 3.3.1 and support for the 2.* interface
  • Date: Tue, 09 Dec 1997 13:44:47 -0700
>From: address@hidden (Dan Schmitt)
>Subject: Netcdf 3.3.1 and support for the 2.* interface
>Organization: Department of Rangeland Ecology and Management, Texas A&M
>Keywords: 199712092018.NAA01206 netCDF 3.3.1 compatibility

Hi Dan,

> The old interface had a define called
> 
>       NC_UNSPECIFIED
> 
> for checking the return value when asking
> about variable types.  This value may not
> be needed anymore (and probably never was
> as everything got a type) but it may break
> code that counted on checking for it.

In the ncvalues.hh in netcdf-3.3.1, the define is still there:

#define NC_UNSPECIFIED ((nc_type)0)

so nothing will break.  We intend to leave it defined for backward
compatibility.

--Russ

_____________________________________________________________________

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu