Add additional comments about new accessor methods

2 files changed, 10 insertions, 1 deletions

diff --git a/manual/design.rst b/manual/design.rst
index cbcded3e..0e50f858 100644
--- a/manual/design.rst
+++ b/manual/design.rst
@@ -746,6 +746,15 @@ and set return values in passed-in pointers, but this would complicate
 both the implementation and the use of the library for a case that is
 actually quite rare and largely avoidable.
 
+*How can I avoid type warnings altogether?* For each
+``getSomethingValue`` accessor that returns a value of the requested
+type and issues a warning for objects of the wrong type, there is also
+a ``getValueAsSomething`` method (since qpdf 10.6) that returns false
+for objects of the wrong type and otherwise returns true and
+initializes a reference. These methods never generate type warnings
+and provide an alternative to explicitly checking the type of an
+object before calling an accessor method.
+
 .. _smart-pointers:
 
 Smart Pointers
diff --git a/manual/release-notes.rst b/manual/release-notes.rst
index b12e5e7f..a2d21ef8 100644
--- a/manual/release-notes.rst
+++ b/manual/release-notes.rst
@@ -99,7 +99,7 @@ For a detailed list of changes, please see the file
 
       - The newer accessor methods return a boolean indicating whether
         or not the object is of the expected type. If it is, a
-        reference of the correct type is returned.
+        reference to a variable of the correct type is initialized.
 
       In many cases, the new interfaces will enable more compact code
       and will also never generate type warnings. Thanks to M. Holger