documentation update

diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi
index 5ccb1590821e56502540d968c7aecf5cdd27dc17..5f097f4f1edd5d60139368dc3d5b29424021e1d9 100644 (file)
--- a/doc/cha-gtls-app.texi
+++ b/doc/cha-gtls-app.texi
@@ -207,12 +207,16 @@ for more information).
 Once the handshake is complete and peer's identity
 has been verified data can be exchanged. The available
 functions resemble the POSIX @code{recv} and @code{send}
-functions.
+functions. It is suggested to use @funcref{gnutls_error_is_fatal}
+to check whether the error codes returned by these functions are
+fatal for the protocol or can be ignored.
 
 @showfuncdesc{gnutls_record_send}
 
 @showfuncdesc{gnutls_record_recv}
 
+@showfuncdesc{gnutls_error_is_fatal}
+
 In DTLS it is adviceable to use the extended receive
 function shown below, because it allows the extraction
 of the sequence number. This is required in DTLS because

diff --git a/lib/gnutls_errors.c b/lib/gnutls_errors.c
index 30d1af7a339c13ea0b748b255de2d762cf860945..cfb3433d0c8a98bed71d41e91135dacb31774358 100644 (file)
--- a/lib/gnutls_errors.c
+++ b/lib/gnutls_errors.c
@@ -341,10 +341,10 @@ static const gnutls_error_entry error_algorithms[] = {
  * @error: is a GnuTLS error code, a negative error code
  *
  * If a GnuTLS function returns a negative error code you may feed that
- * value to this function to see if the error condition is fatal.
- *
- * Note that you may want to check the error code manually, since some
- * non-fatal errors to the protocol may be fatal for you program.
+ * value to this function to see if the error condition is fatal. 
+ * Note that you may also want to check the error code manually, since some
+ * non-fatal errors to the protocol (such as a warning alert or
+ * a rehandshake request) may be fatal for your program.
  *
  * This function is only useful if you are dealing with errors from
  * the record layer or the handshake layer.