summaryrefslogtreecommitdiffstats
path: root/doc/html/Dataspaces.html
diff options
context:
space:
mode:
authorFrank Baker <fbaker@hdfgroup.org>1999-04-26 21:00:15 (GMT)
committerFrank Baker <fbaker@hdfgroup.org>1999-04-26 21:00:15 (GMT)
commitf1a01e0f25d9d229830224236cdb7dadcf6e53d2 (patch)
tree0cdd1fc7e73cd2c79749ab634e44fb1f7970fdc8 /doc/html/Dataspaces.html
parent877a437ad6a028813e0df35ff4e8b19bb341c0cf (diff)
downloadhdf5-f1a01e0f25d9d229830224236cdb7dadcf6e53d2.zip
hdf5-f1a01e0f25d9d229830224236cdb7dadcf6e53d2.tar.gz
hdf5-f1a01e0f25d9d229830224236cdb7dadcf6e53d2.tar.bz2
[svn-r1219] Dataspaces.html
Fixed Bug #292 -- Errors in array-order transversal (C and Fortran orders were reversed) and a minor copy edit.
Diffstat (limited to 'doc/html/Dataspaces.html')
-rw-r--r--doc/html/Dataspaces.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/Dataspaces.html b/doc/html/Dataspaces.html
index 97feff6..d1ae3d1 100644
--- a/doc/html/Dataspaces.html
+++ b/doc/html/Dataspaces.html
@@ -223,14 +223,14 @@ would look like this:
<br><strong>Example 3: Non-contiguous selection with 1,1 offset</strong>
</center>
-<P>Selections also have an linearization ordering of the points selected
+<P>Selections also have a linearization ordering of the points selected
(defaulting to "C" order, ie. last dimension changing fastest). The
linearization order may be specified for each point or it may be chosen by
the axis of the dataspace. For example, with the default "C" ordering,
-example 1's selected points are iterated through in this order: (1,1), (2,1),
-(3,1), (1,2), (2,2), etc. With "FORTRAN" ordering, example 1's selected points
-would be iterated through in this order: (1,1), (1,2), (1,3), (1,4), (1,5),
-(2,1), (2,2), etc.
+example 1's selected points are iterated through in this order: (1,1), (1,2),
+(1,3), (2,1), (2,2), etc. With "FORTRAN" ordering, example 1's selected points
+would be iterated through in this order: (1,1), (2,1), (3,1), (4,1), (5,1),
+(1,2), (2,2), etc.
<P>A dataspace may be stored in the file as a permanent object, to allow many
datasets to use a commonly defined dataspace. Dataspaces with extendable