summaryrefslogtreecommitdiffstats
path: root/windows
diff options
context:
space:
mode:
authorPedro Vicente Nunes <pvn@hdfgroup.org>2004-03-02 18:12:25 (GMT)
committerPedro Vicente Nunes <pvn@hdfgroup.org>2004-03-02 18:12:25 (GMT)
commit931efcb5ebd4099d18d93e7dcdaf296ea4991d73 (patch)
tree045fa2f9825fae4609e73d39b6831f1efa6a3c43 /windows
parent77d3875c5b0787d373165f6b7537081b46e0d031 (diff)
downloadhdf5-931efcb5ebd4099d18d93e7dcdaf296ea4991d73.zip
hdf5-931efcb5ebd4099d18d93e7dcdaf296ea4991d73.tar.gz
hdf5-931efcb5ebd4099d18d93e7dcdaf296ea4991d73.tar.bz2
[svn-r8229] Purpose:
1) new function for tools library 2) new test script for h5repack Description: 1) currently all the tools (h5dump, h5diff, etc) do not check if a filter is available for reading some dataset that might have a filter not available on the current configuration (the behaviour of the tools until now was to trigger a library error, saying that the dataset cannot be read due to the lack of the filter) Solution: 1) added a new function h5tools_canreadf that checks if a dataset can be read depending on the availability of filters. this function was added in calls for h5diff and h5repack. instead of triggering the library error, a message is printed, saying that the dataset cannot be read (the print is optional, it is on on verbose mode) 2) added a shell script that tests the commannd line tool behaviour of h5repack the script does a series of runs of h5repack with several options on the same file (this file test4.h5 was added to the testfiles dir). then, it runs the h5diff tool, with the input and output files , in each run. the goal of the test is also to check item 1) . the binary file was saved with filters that might not be available on other configurations Platforms tested: linux (all filters enabled) linux (some filters disabled) solaris (some filters disabled) AIX (some filters disabled) windows (all filters on and off ) Misc. update:
Diffstat (limited to 'windows')
0 files changed, 0 insertions, 0 deletions