jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Corrected exception specification terminology

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@7054 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2005-03-08 22:08:37 +00:00
commit b7d94f544a
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Doc/Manual/SWIGPlus.html
View file

@ -44,7 +44,7 @@
<li><a href="#SWIGPlus_nn29">Class extension</a>
<li><a href="#SWIGPlus_nn30">Templates</a>
<li><a href="#SWIGPlus_nn31">Namespaces</a>
<li><a href="#SWIGPlus_nn32">Exception specifiers</a>
<li><a href="#SWIGPlus_exception_specifications">Exception specifications</a>
<li><a href="#SWIGPlus_nn33">Pointers to Members</a>
<li><a href="#SWIGPlus_nn34">Smart pointers and operator-&gt;()</a>
<li><a href="#SWIGPlus_nn35">Using declarations and inheritance</a>
@ -3584,7 +3584,7 @@ more advanced namespace support.
</p>
<H2><a name="SWIGPlus_nn32"></a>6.20 Exception specifiers</H2>
<H2><a name="SWIGPlus_exception_specifications"></a>6.20 Exception specifications</H2>
<p>
@ -3627,7 +3627,7 @@ Obviously, the exact details of how exceptions are handled depend on the target
</p>
<p>
Since exception specifiers are sometimes only used sparingly, this alone may not be enough to
Since exception specifications are sometimes only used sparingly, this alone may not be enough to
properly handle C++ exceptions. To do that, a different set of special SWIG directives are used.
Consult the "<a href="Customization.html#Customization">Customization features</a>" chapter for details.
</p>

2
Doc/Manual/Typemaps.html
View file

@ -506,7 +506,7 @@ int foo(<b><font color="#ff0000">int x, double y, char *s</font></b>);
</div>
<ul>
<li>Handling of C++ exception specifiers. ("throw" typemap).</li>
<li>Handling of C++ exception specifications. ("throw" typemap).</li>
</ul>
<p>