[svn-r12171] Purpose:

bug fixes

Description:
h5dump/h5ls were not displaying long doubles correctly

Solution:
1) the print datatype functions were incorrectly testing for the valid return value from H5Tequal,
   (TRUE), causing the display of an incorrect name of a dataype in error cases from H5Tequal
2) h5tools_print_str did not have a case for native long double
3) added a file generator for a long double dataset
4) added one script test for the long double data (commented , some sytems don't have a native long double match, and the output differs)
5) added a vms file and h5dump script test


Platforms tested:
linux 32, 64
solaris
AIX

Misc. update:

1 files changed, 18 insertions, 0 deletions

diff --git a/tools/testfiles/tvms.ddl b/tools/testfiles/tvms.ddl
new file mode 100644
index 0000000..359eab7
--- /dev/null
+++ b/tools/testfiles/tvms.ddl
@@ -0,0 +1,18 @@
+#############################
+Expected output for 'h5dump tvms.h5'
+#############################
+HDF5 "tvms.h5" {
+GROUP "/" {
+   DATASET "IntArray" {
+      DATATYPE  H5T_VAX_F64
+      DATASPACE  SIMPLE { ( 5, 6 ) / ( 5, 6 ) }
+      DATA {
+      (0,0): 0, 1, 2, 3, 4, 5,
+      (1,0): 1, 2, 3, 4, 5, 6,
+      (2,0): 2, 3, 4, 5, 6, 7,
+      (3,0): 3, 4, 5, 6, 7, 8,
+      (4,0): 4, 5, 6, 7, 8, 9
+      }
+   }
+}
+}