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

html fixes

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@8041 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2005-12-22 23:31:02 +00:00
commit 933af2ee87
4 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Doc/Manual/CSharp.html
View file

@ -317,7 +317,7 @@ This feature is useful for some obscure cases where SWIG might get the <tt>virtu
</li>
<li>
<a name="csharp_module_directive">
<a name="csharp_module_directive"></a>
<p>
The name of the intermediary class can be changed from its default, that is, the module name with PINVOKE appended after it.
The module directive attribute <tt>imclassname</tt> is used to achieve this:

10
Doc/Manual/Java.html
View file

@ -2097,6 +2097,7 @@ SWIG uses Java code wherever possible as it is compiled into byte code which req
The functions in the intermediary JNI class cannot be accessed outside of its package. Access to them is gained through the module class for globals otherwise the appropriate proxy class.
</p>
<a name="java_module_directive"></a>
<p>
The name of the intermediary JNI class can be changed from its default, that is, the module name with JNI appended after it.
The module directive attribute <tt>jniclassname</tt> is used to achieve this:
@ -2150,7 +2151,7 @@ The pragma code appears in the generated intermediary JNI class where you would
<div class="code">
<pre>
[ jniclassimports pragma ]
[ jniclassmodifiers pragma ] jniclassname extends [ jniclassbase pragma ]
[ jniclassclassmodifiers pragma ] jniclassname extends [ jniclassbase pragma ]
implements [ jniclassinterfaces pragma ] {
[ jniclasscode pragma ]
... SWIG generated native methods ...
@ -4639,7 +4640,12 @@ These special variables are used in the directors typemaps. See <a href="#java_d
<p>
<b><tt>$module</tt></b><br>
This special variable expands to the module name, as specified by <tt>%module</tt> or the <tt>-module</tt> commandline option.
Useful for constructing the intermediary classname, which is just <tt>$moduleJNI</tt>.
</p>
<p>
<b><tt>$imclassname</tt></b><br>
This special variable expands to the intermediary class name. Usually this is the same as '$moduleJNI',
unless the jniclassname attribute is specified in the <a href="Java.html#java_module_directive">%module directive</a>.
</p>
<H3><a name="typemaps_for_c_and_c++"></a>20.8.7 Typemaps for both C and C++ compilation</H3>

6
Doc/Manual/Library.html
View file

@ -1423,7 +1423,7 @@ For example:
%module example
%include "std_string.i"
%apply const std::string& {std::string* foo};
%apply const std::string&amp; {std::string* foo};
struct my_struct
{
@ -1444,10 +1444,6 @@ print x.foo; # print as string
</pre>
</div>
<p>
</pre>
</div>
<p>
This module only supports types <tt>std::string</tt> and
<tt>const std::string &amp;</tt>. Pointers and non-const references

2
Doc/Manual/Windows.html
View file

@ -250,6 +250,7 @@ SWIG parses ISO C/C++ so cannot deal with proprietary conventions such as <tt>__
There is a Windows interface file, <tt>windows.i</tt>, to deal with these calling conventions though.
The file also contains typemaps for handling commonly used Windows specific types such as <tt>__int64</tt>, <tt>BOOL</tt>, <tt>DWORD</tt> etc.
Include it like you would any other interface file, for example:
</p>
<div class="code"><pre>
%include &lt;windows.i&gt;
@ -257,7 +258,6 @@ Include it like you would any other interface file, for example:
__declspec(dllexport) ULONG __stdcall foo(DWORD, __int32);
</pre></div>
</p>
</body>
</html>