Doc: Updated the exception safety documentation to refer to the Symbian-

specific page.

Reviewed-by: Trust Me

1 files changed, 13 insertions, 1 deletions

diff --git a/doc/src/exceptionsafety.qdoc b/doc/src/exceptionsafety.qdoc
index 4e3e89e..580cb17 100644
--- a/doc/src/exceptionsafety.qdoc
+++ b/doc/src/exceptionsafety.qdoc
@@ -103,7 +103,7 @@
     Note that implicitly shared Qt classes will not throw in their assignment
     operators or copy constructors, so the limitation above does not apply.
 
-    \section1 Out of memory handling
+    \section1 Out of Memory Handling
 
     Most desktop operating systems overcommit memory. This means that \c malloc()
     or \c{operator new} return a valid pointer, even though there is not enough
@@ -141,4 +141,16 @@
     After an exception is thrown, the connection to the windowing server
     might already be closed. It is not safe to call a GUI related function
     after catching an exception.
+
+    \section1 Platform-Specific Exception Handling
+
+    \section2 Symbian (Qt for S60)
+
+    The Symbian platform implements its own exception system that differs from the standard
+    C++ mechanism. When using Qt for S60, and especially when writing code to access Symbian
+    functionality directly, it may be necessary to know about the underlying implementation
+    and how it interacts with Qt.
+
+    The \l{Exception Safety with Symbian} document shows how to use the facilities provided
+    by Qt to use exceptions as safely as possible.
 */