cd7fc2047b
SwigPyBuiltin_SetMetaType. For %import statements, move the runtime import out of SWIG_init and into the .py file. The reason for this is that the import must be executed within the python execution frame of the module, which is true in the .py file, but *not* true in the initialization function. Had to re-order the .py file slightly to put the 'import' statements at the top; that's necessary to make sure base types from an imported module are initialized first. If -builtin isn't used, then the .py code is not re-ordered. Added an explanation and workaround for the limitation that wrapped types are not raise-able. git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/branches/szager-python-builtin@12585 626c5289-ae23-0410-ae9c-e8d60b6d4f22 |
||
|---|---|---|
| .. | ||
| Allegrocl.html | ||
| Arguments.html | ||
| ch2.1.png | ||
| ch9.table.2.png | ||
| ch11.1.png | ||
| ch11.2.png | ||
| ch11.3.png | ||
| ch12.1.png | ||
| chapters | ||
| Chicken.html | ||
| Contents.html | ||
| Contract.html | ||
| CSharp.html | ||
| Customization.html | ||
| D.html | ||
| Extending.html | ||
| fixstyle.py | ||
| Go.html | ||
| Guile.html | ||
| index.html | ||
| Introduction.html | ||
| Java.html | ||
| Library.html | ||
| linkchecker.config | ||
| Lisp.html | ||
| Lua.html | ||
| makechap.py | ||
| Makefile | ||
| maketoc.py | ||
| margin-left.patch | ||
| Modula3.html | ||
| Modules.html | ||
| Mzscheme.html | ||
| Ocaml.html | ||
| Octave.html | ||
| Perl5.html | ||
| Php.html | ||
| Pike.html | ||
| Preface.html | ||
| Preprocessor.html | ||
| Python.html | ||
| R.html | ||
| README | ||
| Ruby.html | ||
| Scripting.html | ||
| Sections.html | ||
| style.css | ||
| SWIG.html | ||
| swig16.png | ||
| SWIGPlus.html | ||
| Tcl.html | ||
| Typemaps.html | ||
| Varargs.html | ||
| Warnings.html | ||
| Windows.html | ||
This directory contains the HTML for the SWIG users manual.
All of this HTML is hand-written. However, section numbering, indices,
and the table of contents is generated automatically by the 'maketoc.py'
script. The Makefile has further information on how the various alternative
forms of the documentation is generated from the hand-written HTML.
There are 4 types of boxes that code or whatever can be inside:
- <div class="shell">...</div>
This is for text that shows the output of running commands on the shell.
- <div class="code">...</div>
This is for either C, C++, or SWIG code
- <div class="targetlang">...</div>
This is for code in a target scripting language
- <div class="diagram">...</div>
This is for text that is not code or a shell
The general format is
<div class="foo"><pre>
whatever here
</pre></div>