> ...the request was to capture the DDL to a file so that the stdout would not > show any text.
h5dump -o data.txt restart0.h5 > /dev/null > A by-product is that one could send the DDL to a file and show just data from > stdout. (h5dump -o data.txt restart0.h5 > ddl.txt ; cat data.txt) > Or if you had a sequence of commands in a script, all DDL and data would go to > files and stdout would just show the the commands that were executed. h5dump -o >(cat >> data.txt) restart0.h5 > >(cat >> ddl.txt) This command can be repeated ad nauseum. It appends to data.txt and ddl.txt on each invocation. My response to the RFC is that this stuff is best left to the shell. The bare minimum support in h5dump is present-- that is, the ability to separate the data and the DDL onto separate files. With that in place, I'd personally not chance the source code of the mostly-sunset h5dump utility. Everything you've described is an intermediate-level, five minute exercise in using pipes. - Rhys _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
