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

netcdf C++ interface futures

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: netcdf C++ interface futures
  • Date: Mon, 28 Apr 1997 15:54:29 -0600
Hello.

We are working on the netcdf version 3 release.
I'm in the process of adapting the netcdf C++
support (src/cxx) to use the new netcdf-3 C interface.

(To read about what's new the netcdf-3 C interface,
have a look at
http://www.unidata.ucar.edu/packages/netcdf/prerelease.html
)

As users of the C++ interface, I wanted to get some feedback
from you. First I've got some generic questions, and then
some very specific ones.

1) Are your systems which use the netcdf C++ interface under active
development? Or is it more a "finished" product where there are few
changes.

2) What platform and C++ compiler combinations are you _currently_
using? (For example, SunOS 5 Sun C++ 4.2)

3) Does you C++ development environment support exceptions? templates?
Do you use these features?


In the netcdf-3 C interface, we eliminated the 'ncerr' and
'ncopts' globals. (These are still available in a backward
compatibility interface.) The C++ NcError class provides an
interface to these globals.

4) Do you make calls to NcError::NcError(Behavior) to change away
from the default behavior? (The default behavior is 'verbose_fatal' which
prints a message and exits on error.)

5) How severely would it impact your system if the NcError member functions
became noops and instead the netcdf C++ interface threw exceptions?

6) (optional) If you could change 2 things about the C++ interface,
what would they be.

Thanks for your time.

-glenn