Hi Quincey, Thanks for the very quick response.
>> I've noticed (from trying it and then reading the 1.8.7 source in >> H5A.c) that H5Aopen seemingly never returns H5E_NOTFOUND. The logic >> that I suspect should return H5E_NOTFOUND instead returns >> H5E_CANTINIT... > Yes, we should tweak that, but really it's best to use H5Aexists first, > if the application isn't certain that the attribute should exist. True, but it is nice to pay for the existence check overhead only in the uncommon failure case (though I expect the overhead to be miniscule). I'll use H5Aexists in my logic to clarify the situation after H5Aopen has balked. FWIW, H5Aopen_by_name exhibits different behavior from H5Aopen but also does not return H5E_NOTFOUND. - Rhys _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
