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.
> > To: address@hidden > > From: "Nigel O'Brian" <address@hidden> > > Subject: Minor bug in NetCDF 2.4 > > Organization: School of Mathematics, University of Sydney > > Keywords: 199708110100.TAA07093 > > You can define a variable called "", but accessing the > > variable in the resulting file causes a segmentation > > fault. According to the documentation "" should not be > > accepted. Russ replies: > However, the current version still permits the definition of a variable > with the name "". I think we should not continue to permit this as a > variable name, even if the Perl and Python interfaces would support it, > because applications and visualization systems for netCDF data might > have problems with empty names. Also their is no CDL syntax to declare > a variable with the name "". Fixed. Minor change to libsrc/string.c, added test to nc_test/test_put.m4. -glenn