summaryrefslogtreecommitdiffstats
path: root/doc/html/RM_H5F.html
diff options
context:
space:
mode:
authorFrank Baker <fbaker@hdfgroup.org>2001-07-06 02:32:06 (GMT)
committerFrank Baker <fbaker@hdfgroup.org>2001-07-06 02:32:06 (GMT)
commitcfa36589316578e0fd6b1f315b48bffc0bf745d0 (patch)
tree0e0042d948eaa355bd7aab61cf385f70073afaeb /doc/html/RM_H5F.html
parent1af1fe8d8af227d11cb10c7c65a7dfee90377bf3 (diff)
downloadhdf5-cfa36589316578e0fd6b1f315b48bffc0bf745d0.zip
hdf5-cfa36589316578e0fd6b1f315b48bffc0bf745d0.tar.gz
hdf5-cfa36589316578e0fd6b1f315b48bffc0bf745d0.tar.bz2
[svn-r4126] Purpose:
Bugfixes and editing. Description: RM_H5T.html H5Tget_class -- Added H5T_ARRAY to list of valid datatype class IDs. Closes bug #611. -- Minor formatting issue in same command. RM_H5F.html H5Fflush -- Added "Note:" re H5 vs OS buffers. H5Fclose -- Corrected mentions of H5close to read H5Fclose. RM_H5P.html Removed () from several H5* function names in running text. Platforms tested: IE 5
Diffstat (limited to 'doc/html/RM_H5F.html')
-rw-r--r--doc/html/RM_H5F.html10
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/html/RM_H5F.html b/doc/html/RM_H5F.html
index 0f15852..fbcbcc2 100644
--- a/doc/html/RM_H5F.html
+++ b/doc/html/RM_H5F.html
@@ -291,6 +291,12 @@ facilitate moving easily between them.</i>
<td align=left valign=bottom>Flushes only the specified file.</td></tr>
</table>
</center>
+<dt><strong>Note:</strong>
+ <dd>HDF5 does not possess full control over buffering.
+ <code>H5Fflush</code> flushes the internal HDF5 buffers then
+ asks the operating system (the OS) to flush the system buffers for the
+ open files. After that, the OS is responsible for ensuring that
+ the data is actually flushed to disk.
<dt><strong>Parameters:</strong>
<dl>
<dt><em>hid_t </em><code>object_id</code>
@@ -447,11 +453,11 @@ facilitate moving easily between them.</i>
<p>
<strong>EXCEPTION:</strong>
Note the following deviation from the above-described behavior.
- If <code>H5close</code> is called for a file but one or more
+ If <code>H5Fclose</code> is called for a file but one or more
objects within the file remain open, those objects will remain
accessible until they are individually closed.
Thus, if the dataset <code>data_sample</code> is open when
- <code>H5close</code> is called for the file containing it,
+ <code>H5Fclose</code> is called for the file containing it,
<code>data_sample</code> will remain open and accessible
(including writable) until it is explicitely closed.
The file will be automatically closed once all objects in the