summaryrefslogtreecommitdiff
path: root/documentation/exceptions.html
diff options
context:
space:
mode:
authorEmiel Bruijntjes <emiel.bruijntjes@copernica.com>2014-03-13 10:50:56 +0100
committerEmiel Bruijntjes <emiel.bruijntjes@copernica.com>2014-03-13 10:50:56 +0100
commitd724e346b28df9907a2ec115d20416944ea10d8a (patch)
treed9ff51e81c8ca5c77e53865a190eac999cc94556 /documentation/exceptions.html
parent3bb0e31416994b0a36b784c8278b1c5f33999b1d (diff)
added id to all h2 tags to make it possible to link to specific sections, update documentation about serializable, fixed compile error for serialize implementation
Diffstat (limited to 'documentation/exceptions.html')
-rw-r--r--documentation/exceptions.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/exceptions.html b/documentation/exceptions.html
index fb4ec52..c4f0e5c 100644
--- a/documentation/exceptions.html
+++ b/documentation/exceptions.html
@@ -78,7 +78,7 @@ exception caught
is as if you're not even working in two different languages, and you can
simply throw a Php::Exception object as if it was a regular PHP exception.
</p>
-<h2>Catching exceptions in C++</h2>
+<h2 id="catching-exceptions">Catching exceptions in C++</h2>
<p>
And this works the other way around too. If your extension calls a PHP
function, and that PHP function happens to throw an exception, you can catch it