Ncgen is unable to resolve
ambiguous references to an enum
constant when two different enums
have same econstant name.
Solved by allowing more specific
forms for econstant references.
1. /.../enumname.enumconstname
2. enumname.enumconstname
3. enumconstname
Case 1 is resolved by using the econstant
in the specific enum definition. If none is
found, an error is reported.
Case 2 is resolved by
1. finding an enclosing group with an
enum definition with the specified name
and containing the specified econstant.
If there are more than one, then an error is reported
2. finding all enum definitions in the dataset that have
the specified enum name and contain the specified
econstant. If more than one is found, then an error is reported.
If the above two methods fail, then report an error.
Case 3 is similar to case 2, but all enums, irrespective
of name are used if they contains the specified enum constant.
The ref_tst_econst.cdl test in ncdump is causing ncdump
to fail. So there may be yet some problem.
Added information about needing to generate configure scripts with 'autoreconf'.
Updated Building with CMake documentation, moved 4.3.0 errata to a place of less prominence.
transition document.
Remoted plain text release_notes moving forward. Created a markdown
version of the README file as an experiment to see what we think.
GitHub will render markdown natively, as does Doxygen and our new
build system.
-DENABLE_DYNAMIC_LOADING to cmake-based builds.
This will allow for compatibility with hdf5 1.8.11 builds that
have enabled dynamic building (depends on libdl).
See Jira ticket NCF-258
