[netcdfgroup] netCDF-C 4.3.3-rc2 available

• To: "netcdfgroup@xxxxxxxxxxxxxxxx List" <netcdfgroup@xxxxxxxxxxxxxxxx>
• Subject: [netcdfgroup] netCDF-C 4.3.3-rc2 available
• From: Ward Fisher <wfisher@xxxxxxxx>
• Date: Thu, 25 Sep 2014 11:34:39 -0600

Hello all,

The second release candidate for netcdf-c 4.3.3 is now available for
download from the Unidata github repository.

   - Source Download:
   https://github.com/Unidata/netcdf-c/releases/tag/v4.3.3-rc2
   - Windows Download:
   http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html
   - Documentation: http://www.unidata.ucar.edu/software/netcdf/docs_rc/
   - Full Release Notes:
   https://github.com/Unidata/netcdf-c/blob/master/RELEASE_NOTES.md

If there any issues with or questions about this pre-release, please let us
know!

Thanks all,

-Ward
Release Highlights

   -

   Fixed the code for handling character constants
   in datalists in ncgen. Two of the problems were:
    1. It failed on large constants
      2. It did not handle e.g. var = ‘a’, ‘b’, …
      in the same way that ncgen3 did.
      See NCF-309 <https://bugtracking.unidata.ucar.edu/browse/NCF-309>.
    -

   Added a new file, netcdf_meta.h. This file is generated automatically at
   configure time and contains information related to the capabilities of the
   netcdf library. This file may be used by projects dependent upon netcdf
   to make decisions during configuration, based on how the netcdf library
   was built. The macro NC_HAVE_META_H is defined in netcdf.h. Paired with
   judicious use of #ifdef‘s, this macro will indicate to developers
   whether or not the meta-header file is present. See NCF-313
   <https://bugtracking.unidata.ucar.edu/browse/NCF-313>.

   Determining the presence of netcdf_meta.h can also be accomplished by
   methods common to autotools and cmake-based build systems.

    -

   Changed Doxygen-generated documentation hosted by Unidata to use more
   robust server-based searching.
    - Corrected embedded URLs in release notes.
   - Corrected an issue where building with HDF4 support with Visual Studio
   would fail.

​