diff options
author | Pedro Vicente Nunes <pvn@hdfgroup.org> | 2008-10-27 20:06:28 (GMT) |
---|---|---|
committer | Pedro Vicente Nunes <pvn@hdfgroup.org> | 2008-10-27 20:06:28 (GMT) |
commit | f08f9340a7cfb323f3565e63b1cfe0604e02b4e5 (patch) | |
tree | 8ff4202ed3f3dfa379c2f68dfafba220f80268e0 /tools/h5dump/testh5dump.sh.in | |
parent | 64e96385de36e41834c7d7de23083ee8b250a579 (diff) | |
download | hdf5-f08f9340a7cfb323f3565e63b1cfe0604e02b4e5.zip hdf5-f08f9340a7cfb323f3565e63b1cfe0604e02b4e5.tar.gz hdf5-f08f9340a7cfb323f3565e63b1cfe0604e02b4e5.tar.bz2 |
[svn-r15969]
Introduced a new feature in the tools library regarding command line parsing
In the definition of arguments, an "*" means that the switch can or can not have an optional argument. This "*" is put in the code regarding the letter definition, and it is transparent to the user (e.g b* instead of the previous b: ), where ":" notes a required argument after the letter (and no ":" or "*" notes no argument, mandatory)
Used for the h5dump binary option -b
It can be now
1) -b (defaults to NATIVE)
2) - b NATIVE
3) - b FILE
4) -b LE
5) -b BE
Note: the keyword NATIVE replaces MEMORY
This feature (-b with no argument) was tested with the sequence of h5dump to binary (NATIVE) then h5import to generate an HDF5 file from the binary file and h5diff to compare the 2 HDF5 files
Tested: windows, linux
Diffstat (limited to 'tools/h5dump/testh5dump.sh.in')
-rw-r--r-- | tools/h5dump/testh5dump.sh.in | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/tools/h5dump/testh5dump.sh.in b/tools/h5dump/testh5dump.sh.in index 9c36594..990ef2a 100644 --- a/tools/h5dump/testh5dump.sh.in +++ b/tools/h5dump/testh5dump.sh.in @@ -463,22 +463,30 @@ TOOLTEST tvms.ddl tvms.h5 # test for binary output TOOLTEST1 tbin1.ddl -d integer -o $TESTDIR/out1.bin -b LE tbinary.h5 -TOOLTEST1 tbin2.ddl -d float -o $TESTDIR/out2.bin -b BE tbinary.h5 -# the MEMORY test can be validated with h5import/h5diff -TOOLTEST1 tbin3.ddl -d integer -o $TESTDIR/out3.bin -b MEMORY tbinary.h5 +# NATIVE default. the NATIVE test can be validated with h5import/h5diff +TOOLTEST1 tbin1.ddl -d integer -o $TESTDIR/out1.bin -b tbinary.h5 +IMPORTTEST $TESTDIR/out1.bin -c out3.h5import -o $TESTDIR/out1.h5 +DIFFTEST tbinary.h5 $TESTDIR/out1.h5 /integer /integer + +TOOLTEST1 tbin2.ddl -b BE -d float -o $TESTDIR/out2.bin tbinary.h5 + +# the NATIVE test can be validated with h5import/h5diff +TOOLTEST1 tbin3.ddl -d integer -o $TESTDIR/out3.bin -b NATIVE tbinary.h5 IMPORTTEST $TESTDIR/out3.bin -c out3.h5import -o $TESTDIR/out3.h5 DIFFTEST tbinary.h5 $TESTDIR/out3.h5 /integer /integer -TOOLTEST1 tbin4.ddl -d double -o $TESTDIR/out4.bin -b FILE tbinary.h5 +TOOLTEST1 tbin4.ddl -d double -b FILE -o $TESTDIR/out4.bin tbinary.h5 # Clean up binary output files if test -z "$HDF5_NOCLEANUP"; then rm -f $TESTDIR/out[1-4].bin + rm -f $TESTDIR/out1.h5 rm -f $TESTDIR/out3.h5 fi + # test for dataset region references TOOLTEST tdatareg.ddl tdatareg.h5 |