mirror of
https://github.com/HDFGroup/hdf5.git
synced 2024-11-21 01:04:10 +08:00
[svn-r1375]
updated the ddl so it has the new types that we are displaying in dumper
This commit is contained in:
parent
c4c6318e6a
commit
c04c1b6abf
@ -93,7 +93,7 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
|
||||
<dir>
|
||||
<pre>
|
||||
<file> ::= HDF5 "<file_name>" { <file_boot_block><FONT SIZE=1.7>opt</FONT> <root_group> }
|
||||
<file> ::= HDF5 <file_name> { <file_boot_block><FONT SIZE=1.7>opt</FONT> <root_group> }
|
||||
|
||||
<file_name> ::= <identifier>
|
||||
|
||||
@ -103,7 +103,7 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
|
||||
<root_group> ::= GROUP "/" { <unamed_datatype>* <group_attribute>* <group_member>* }
|
||||
|
||||
<unamed_datatype> ::= DATATYPE "<unamed_type_name>" { <compound_type> }
|
||||
<unamed_datatype> ::= DATATYPE <unamed_type_name> { <compound_type> }
|
||||
|
||||
<unamed_type_name> ::= the assigned name for unamed type is in the form of
|
||||
#oid1:oid2, where oid1 and oid2 are the object ids of the type
|
||||
@ -112,9 +112,10 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
|
||||
<member_type_def> ::= <scalar_type_def> | <array_type_def>
|
||||
|
||||
<scalar_type_def> ::= <atomic_type> "<field_name>" ;
|
||||
<scalar_type_def> ::= <atomic_type> <field_name> ;
|
||||
|
||||
<atomic_type> ::= <integer> | <float> | <time> | <string> | <bitfield> | <opaque>
|
||||
<atomic_type> ::= <integer> | <float> | <time> | <string> | <bitfield> | <opaque> |
|
||||
<reference> | <enum>
|
||||
|
||||
<integer> ::= H5T_STD_I8BE | H5T_STD_I8LE | H5T_STD_I16BE | H5T_STD_I16LE | H5T_STD_I32BE |
|
||||
H5T_STD_I32LE | H5T_STD_I64BE | H5T_STD_I64LE | H5T_STD_U8BE |
|
||||
@ -146,15 +147,17 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
|
||||
<opaque> ::= TBD
|
||||
|
||||
<reference> ::= H5T_REFERENCE
|
||||
|
||||
<field_name> ::= <identifier>
|
||||
|
||||
<array_type_def> ::= <atomic_type> "<field_name>" <dim_sizes> ;
|
||||
<array_type_def> ::= <atomic_type> <field_name> <dim_sizes> ;
|
||||
|
||||
<dim_sizes> ::= [dimsize1][dimzise2]..., where dimsize1, dimsize2 are integers
|
||||
<dim_sizes> ::= [dimsize1][dimsize2]..., where dimsize1, dimsize2 are integers
|
||||
|
||||
<group_attribute> ::= <attribute>
|
||||
|
||||
<attribute> ::= ATTRIBUTE "<attr_name>" { <datatype>
|
||||
<attribute> ::= ATTRIBUTE <attr_name> { <datatype>
|
||||
<dataspace>
|
||||
<data><FONT SIZE=1.7>opt</FONT> }
|
||||
// <datatype> and <dataspace> must appear before <data>.
|
||||
@ -162,17 +165,25 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
<attr_name> ::= <identifier>
|
||||
|
||||
<datatype> ::= DATATYPE { <atomic_type> } |
|
||||
DATATYPE { <compound_type> }
|
||||
DATATYPE { <compound_type> } |
|
||||
DATATYPE { <named_type> }
|
||||
|
||||
<named_type> ::= "<path_name>"
|
||||
<enum> ::= H5T_ENUM { <integer>; <enum_def>+ }
|
||||
|
||||
<enum_def> ::= <enum_symbol> <enum_val>;
|
||||
|
||||
<enum_symbol> ::= <identifier>
|
||||
|
||||
<enum_val> ::= an integer;
|
||||
|
||||
<named_type> ::= <path_name>
|
||||
|
||||
<path_name> ::= <identifier>
|
||||
|
||||
<dataspace> ::= DATASPACE { SCALAR } |
|
||||
DATASPACE { SIMPLE <current_dims> / <max_dims> } |
|
||||
DATASPACE { COMPLEX <ds_definition>+ }
|
||||
DATASPACE { "<dataspace_name>" } |
|
||||
DATASPACE { <dataspace_name> } |
|
||||
|
||||
<current_dims> ::= (<i>i<FONT SIZE=1.0>1</i></FONT>, <i>i<FONT SIZE=1.0>2</i></FONT>, ... ), where <i>i<FONT SIZE=1.0>k</i></FONT> is an integer, <i>k</i> = 1,2,...
|
||||
|
||||
@ -186,9 +197,46 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
|
||||
<scalar_space_data> ::= <atomic_scalar_data> | <compound_scalar_data>
|
||||
|
||||
<atomic_scalar_data> :: = the value of data
|
||||
<atomic_scalar_data> :: = <integer_data> | <float_data> | <time_data> | <string_data> |
|
||||
<bitfield_data> | <opaque_data> | <enum_data> | <reference_data>
|
||||
|
||||
<integer_data> ::= an integer
|
||||
|
||||
<float_data> ::= a floating point number
|
||||
|
||||
<time_data> ::= TBD
|
||||
|
||||
<string_data> ::= a string
|
||||
// A string is enclosed in double quotes.
|
||||
// If a string is displayed on more than one line, string concatenate operator '//' is used.
|
||||
// If a string is displayed on more than one line, string concatenate operator '//'is used.
|
||||
|
||||
<bitfield_data> ::= TBD
|
||||
|
||||
<opaque_data> ::= TBD
|
||||
|
||||
<enum_data> ::= an integer
|
||||
//maybe will be <enum_symbol> in the future
|
||||
|
||||
<reference_data> ::= <object_ref_data> | <data_region_data> | NULL
|
||||
|
||||
<object_ref_data> ::= <object_type> <object_id>
|
||||
|
||||
<object_type> ::= DATASET | GROUP | DATATYPE
|
||||
|
||||
<object_id> ::= an integer:an integer
|
||||
|
||||
<data_region_data> ::= H5T_STD_REF_DSETREG <object_id> {<data_region_data_info>,
|
||||
<data_region_data_info>, ...}
|
||||
|
||||
<data_region_data_info> ::= <region_info> | <point_info>
|
||||
|
||||
<region_info> ::= (<lower_bound>:<upper_bound>, <lower_bound>:<upper_bound>, ...)
|
||||
|
||||
<lower_bound> ::= an integer
|
||||
|
||||
<upper_bound> ::= an integer
|
||||
|
||||
<point_info> ::= (an integer, an integer, ...)
|
||||
|
||||
<compound_scalar_data> ::= { [ <member_data> ], [ <member_data> ], ... }
|
||||
|
||||
@ -209,21 +257,21 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
<group_member> ::= <named_datatype> | <named_dataspace> | <group> | <dataset> |
|
||||
<softlink>
|
||||
|
||||
<named_datatype> ::= DATATYPE "<type_name>" { <compound_type> }
|
||||
<named_datatype> ::= DATATYPE <type_name> { <compound_type> }
|
||||
|
||||
<type_name> ::= <identifier>
|
||||
|
||||
<named_dataspace> ::= TBD
|
||||
|
||||
<group> ::= GROUP "<group_name>" { <hardlink> } |
|
||||
GROUP "<group_name>" { <group_attribute>* <group_member>* }
|
||||
<group> ::= GROUP <group_name> { <hardlink> } |
|
||||
GROUP <group_name> { <group_attribute>* <group_member>* }
|
||||
|
||||
<group_name> ::= <identifier>
|
||||
|
||||
<hardlink> ::= HARDLINK "<path_name>"
|
||||
<hardlink> ::= HARDLINK <path_name>
|
||||
|
||||
<dataset> ::= DATASET "<dataset_name>" { <hardlink> } |
|
||||
DATASET "<dataset_name>" { <datatype>
|
||||
<dataset> ::= DATASET <dataset_name> { <hardlink> } |
|
||||
DATASET <dataset_name> { <datatype>
|
||||
<dataspace>
|
||||
<storagelayout><FONT SIZE=1.7>opt</FONT>
|
||||
<compression><FONT SIZE=1.7>opt</FONT>
|
||||
@ -259,7 +307,7 @@ This section contains a brief explanation of the symbols used in the DDL.
|
||||
|
||||
<dataset_attribute> ::= <attribute>
|
||||
|
||||
<softlink> ::= SOFTLINK "<softlink_name>" { LINKTARGET "<target>" }
|
||||
<softlink> ::= SOFTLINK <softlink_name> { LINKTARGET <target> }
|
||||
|
||||
<softlink_name> ::= <identifier>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user