hdf5/tools/testfiles/tdataregbe.ls

Opened "tdatareg.h5" with sec2 driver.
Dataset1                 Dataset {4/4}
    Location:  1:1284
    Links:     1
    Storage:   information not available
    Type:      dataset region reference
Dataset2                 Dataset {10/10, 10/10}
    Location:  1:744
    Links:     1
    Storage:   100 logical bytes, 100 allocated bytes, 100.00% utilization
    Type:      native unsigned char
[svn-r16299] Print a message of Storage: information not available When displaying storage information for VL and dataset region types Added 2 shell runs that display this information #818 Tested: windows, linux 2009-01-13 23:37:37 +08:00			`Opened "tdatareg.h5" with sec2 driver.`
			`Dataset1 Dataset {4/4}`
			`Location: 1:1284`
			`Links: 1`
			`Storage: information not available`
			`Type: dataset region reference`
			`Dataset2 Dataset {10/10, 10/10}`
			`Location: 1:744`
			`Links: 1`
			`Storage: 100 logical bytes, 100 allocated bytes, 100.00% utilization`
[svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output) the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other tested: h5committest 2009-02-27 04:21:50 +08:00			`Type: native unsigned char`