From 6df5f12527a221cde2b8f0ed08f7154c9609a8b3 Mon Sep 17 00:00:00 2001 From: Larry Knox Date: Wed, 15 Mar 2023 18:15:43 -0500 Subject: Update ReferenceManual.dox (#2517) (#2569) Co-authored-by: mattjala <124107509+mattjala@users.noreply.github.com> --- doxygen/dox/ReferenceManual.dox | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doxygen/dox/ReferenceManual.dox b/doxygen/dox/ReferenceManual.dox index b9bcd49..40f8b8a 100644 --- a/doxygen/dox/ReferenceManual.dox +++ b/doxygen/dox/ReferenceManual.dox @@ -158,7 +158,7 @@ Follow these simple rules and stay out of trouble: \li \Bold{Dynamic memory allocation:} The API contains a few functions in which the HDF5 library dynamically allocates memory on the caller's behalf. The caller owns this memory and eventually must free it by calling H5free_memory() and not language-explicit memory functions. -\li \Bold{Be careful with that saw:} Do not modify the underlying collection when an +\li \Bold{Don't modify while iterating:} Do not modify the underlying collection when an iteration is in progress! \li \Bold{Use of locations:} Certain API functions, typically called \Code{H5***_by_name} use a combination of identifiers and path names to refer to HDF5 objects. -- cgit v0.12