diff options
author | Quincey Koziol <koziol@hdfgroup.org> | 2000-11-14 00:05:05 (GMT) |
---|---|---|
committer | Quincey Koziol <koziol@hdfgroup.org> | 2000-11-14 00:05:05 (GMT) |
commit | 7b8b71ed9ba2d5b78cdfd50f719296e5f62a5dc5 (patch) | |
tree | c237dbddd391c545b7285e3bf3219e2db3aec439 /src | |
parent | f6a92e75600be0b77306893034a8d3982f91ff20 (diff) | |
download | hdf5-7b8b71ed9ba2d5b78cdfd50f719296e5f62a5dc5.zip hdf5-7b8b71ed9ba2d5b78cdfd50f719296e5f62a5dc5.tar.gz hdf5-7b8b71ed9ba2d5b78cdfd50f719296e5f62a5dc5.tar.bz2 |
[svn-r2891] Purpose:
Bug fix.
Description:
Generic property list code wasn't getting initialized early enough to get
the proper values into the macro/constants.
Solution:
Call H5P_init() from H5_init_library().
Platforms tested:
FreeBSD 4.1.1 (hawkwind)
Diffstat (limited to 'src')
-rw-r--r-- | src/H5.c | 18 |
1 files changed, 10 insertions, 8 deletions
@@ -117,21 +117,23 @@ H5_init_library(void) * Initialize interfaces that might not be able to initialize themselves * soon enough. The file & dataset interfaces must be initialized because * calling H5Pcreate() might require the file/dataset property classes to be - * initialized. The property lists are be initialized during the H5F/H5D - * init calls (because they call H5P functions, which initialize the H5P - * API, before using the properties). + * initialized. */ if (H5F_init()<0) { - HRETURN_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, - "unable to initialize file interface"); + HRETURN_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, + "unable to initialize file interface"); } if (H5T_init()<0) { HRETURN_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, - "unable to initialize type interface"); + "unable to initialize type interface"); } if (H5D_init()<0) { - HRETURN_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, - "unable to initialize file interface"); + HRETURN_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, + "unable to initialize dataset interface"); + } + if (H5P_init()<0) { + HRETURN_ERROR(H5E_FUNC, H5E_CANTINIT, FAIL, + "unable to initialize property list interface"); } /* Debugging? */ |