summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorFrank Baker <fbaker@hdfgroup.org>2000-07-17 18:21:39 (GMT)
committerFrank Baker <fbaker@hdfgroup.org>2000-07-17 18:21:39 (GMT)
commitca21737873d4e4fd169bbcef7abd831a2f2fe42b (patch)
tree185a1187dd9dfe9c2bc3cebf4a3605a04b09b3b1 /doc
parent354ca36dc79dc0e6fc324f86d169ca02713ffff9 (diff)
downloadhdf5-ca21737873d4e4fd169bbcef7abd831a2f2fe42b.zip
hdf5-ca21737873d4e4fd169bbcef7abd831a2f2fe42b.tar.gz
hdf5-ca21737873d4e4fd169bbcef7abd831a2f2fe42b.tar.bz2
[svn-r2434] H5.intro.html
Datatypes.html Fixed confusing references to "simple datatypes." Minor edits.
Diffstat (limited to 'doc')
-rw-r--r--doc/html/Datatypes.html6
-rw-r--r--doc/html/H5.intro.html8
2 files changed, 10 insertions, 4 deletions
diff --git a/doc/html/Datatypes.html b/doc/html/Datatypes.html
index bc4a9e0..71cf733 100644
--- a/doc/html/Datatypes.html
+++ b/doc/html/Datatypes.html
@@ -2431,13 +2431,13 @@ in the HDF5 distribution.
<h2>10. Sharing Datatypes among Datasets</h2>
- <p>If a file has lots of datasets which have a common datatype
+ <p>If a file has lots of datasets which have a common datatype,
then the file could be made smaller by having all the datasets
share a single datatype. Instead of storing a copy of the
datatype in each dataset object header, a single datatype is stored
and the object headers point to it. The space savings is
- probably only significant for datasets with a compound datatype
- since the simple datatypes can be described with just a few
+ probably only significant for datasets with a compound datatype,
+ since the atomic datatypes can be described with just a few
bytes anyway.
<p>To create a bunch of datasets that share a single datatype
diff --git a/doc/html/H5.intro.html b/doc/html/H5.intro.html
index 9d9afb1..4f09c3a 100644
--- a/doc/html/H5.intro.html
+++ b/doc/html/H5.intro.html
@@ -390,7 +390,13 @@ Atomic datatypes can also be system-specific, or <I><CODE>NATIVE</CODE></I>, and
<FONT FACE="Times"><P>See <A HREF="Datatypes.html"><I>Datatypes</I></A> in the<I> HDF User&#146s Guide</I> for further information.</font>
-<FONT FACE="Times"><P>A <I>compound datatype</I> is one in which a collection of simple datatypes are represented as a single unit, similar to a <I>struct</I> in C. The parts of a compound datatype are called <I>members.</I> The members of a compound datatype may be of any datatype, including another compound datatype. It is possible to read members from a compound type without reading the whole type.
+<FONT FACE="Times"><P>A <I>compound datatype</I> is one in which a
+collection of several datatypes are represented as a single unit,
+a compound datatype, similar to a <I>struct</I> in C.
+The parts of a compound datatype are called <I>members.</I>
+The members of a compound datatype may be of any datatype,
+including another compound datatype. It is possible to read members
+from a compound type without reading the whole type.
<p>
<ta/FONT><I><P>Named datatypes.</I> Normally each dataset has its own datatype, but sometimes we may want to share a datatype among several datasets. This can be done using a <I>named </I>datatype. A named datatype is stored in the file independently of any dataset, and referenced by all datasets that have that datatype. Named datatypes may have an associated attributes list.
See <A HREF="Datatypes.html"><I>Datatypes</I></A></font><FONT FACE="Times"> in the<I> HDF User&#146s Guide</I> for further information.