mirror/netcdf-c
2
0
Fork 0
mirror of https://github.com/Unidata/netcdf-c.git synced 2025-01-18 15:55:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

[NCF-265] again.

Browse Source 
1. Updated the ncgen manual (ncgen.1)
   to discuss handling of ambiguous
   enumeration constant references.
2. Fixed the test case. It is currently
   XFAIL'd until such time as ncdump
   is modified to output properly
   disambiguated enumeration constant
   references.
This commit is contained in:
dmh 2013-09-22 12:08:27 -06:00
parent 06d91c3084
commit e7414e16d0
3 changed files with 21 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ncdump/expected4/ref_tst_econst.dmp
View File

@ -1,16 +1,16 @@
netcdf tst_econst {
netcdf ref_tst_econst {
types:
byte enum e1 {pass = 0, fail = 1, undefined = 2} ;
byte enum e2 {defined = 0, undefined = 1} ;
variables:
e1 test1 ;
e2 test2 ;
e2 test3 ;
e1 test3 ;
data:
test1 = pass ;
test2 = undefined;
test3 = undefined;
test3 = fail;
}

2
ncdump/tst_netcdf4.sh
View File

@ -86,3 +86,5 @@ diff -b tst_special_atts.cdl $srcdir/ref_tst_special_atts.cdl
echo "*** All ncgen and ncdump test output for netCDF-4 format passed!"
exit 0

18
ncgen/ncgen.1
View File

@ -216,7 +216,7 @@ netcdf foo { // an example netCDF specification in CDL
\fBvariables\fP:
/g/\fIcmpd_t\fP compoundvar;
\fBdata\fP:
compoundvar = { {3,4,5}, Stratus } ;
compoundvar = { {3,4,5}, enum_t.Stratus } ;
} // group h
}
.fi
@ -656,7 +656,7 @@ When name is not prefixed, then scope rules are applied to locate the
specified declaration. Currently, there are three rules: one for dimensions,
one for types and enumeration constants, and one for all others.
.HP
1. When an unprefixed name of a dimension is used (as in a
When an unprefixed name of a dimension is used (as in a
variable declaration), ncgen first looks in the immediately
enclosing group for the dimension. If it is not found
there, then it looks in the group enclosing this group.
@ -674,6 +674,20 @@ is "highest" in the group hierarchy.
One final note. Forward references are not allowed.
This means that specifying, for example,
/g1/g2/t1 will fail if this reference occurs before g1 and/or g2 are defined.
.SS "Specifying Enumeration Constants"
.LP
References to Enumeration constants (in data lists) can be ambiguous
since the same enumeration constant name can be defined in more than
one enumeration. If a cdl file specified an ambiguous constant,
then ncgen will signal an error. Such constants can be disambiguated
in two ways.
.IP "\fB1.\fP"
Prefix the enumeration constant with the name of the enumeration separated
by a dot: \fIenum.econst\fP, for example.
.IP "\fB2.\fP"
If case one is not sufficient to disambiguate the enumeration constant,
then one must specify the precise enumeration type using
a group path: \fI/g1/g2/enum.econst\fP, for example.
.SS "Special Attributes"
.LP
Special, virtual, attributes can be specified to provide