32.1 Overview

33.1 Overview

@@ -155,10 +155,10 @@ described followed by a discussion of low-level implementation details.

32.2 Preliminaries

33.2 Preliminaries

32.2.1 Running SWIG

33.2.1 Running SWIG

@@ -256,7 +256,7 @@ The following sections have further practical examples and details on how you might go about compiling and using the generated files.

32.2.2 Using distutils

33.2.2 Using distutils

@@ -348,7 +348,7 @@ This same approach works on all platforms if the appropriate compiler is install can even build extensions to the standard Windows Python using MingGW)

32.2.3 Hand compiling a dynamic module

33.2.3 Hand compiling a dynamic module

@@ -396,7 +396,7 @@ module actually consists of two files; socket.py and

32.2.4 Static linking

33.2.4 Static linking

@@ -475,7 +475,7 @@ If using static linking, you might want to rely on a different approach (perhaps using distutils).

32.2.5 Using your module

33.2.5 Using your module

@@ -632,7 +632,7 @@ system configuration (this requires root access and you will need to read the man pages).

32.2.6 Compilation of C++ extensions

33.2.6 Compilation of C++ extensions

@@ -724,7 +724,7 @@ erratic program behavior. If working with lots of software components, you might want to investigate using a more formal standard such as COM.

32.2.7 Compiling for 64-bit platforms

33.2.7 Compiling for 64-bit platforms

@@ -761,7 +761,7 @@ and -m64 allow you to choose the desired binary format for your python extension.

32.2.8 Building Python Extensions under Windows

33.2.8 Building Python Extensions under Windows

@@ -870,7 +870,7 @@ SWIG Wiki.

32.3 A tour of basic C/C++ wrapping

33.3 A tour of basic C/C++ wrapping

@@ -879,7 +879,7 @@ to your C/C++ code. Functions are wrapped as functions, classes are wrapped as This section briefly covers the essential aspects of this wrapping.

32.3.1 Modules

33.3.1 Modules

@@ -892,7 +892,7 @@ module name, make sure you don't use the same name as a built-in Python command or standard module name.

32.3.2 Functions

33.3.2 Functions

@@ -916,7 +916,7 @@ like you think it does: >>>

32.3.3 Global variables

33.3.3 Global variables

@@ -1054,7 +1054,7 @@ that starts with a leading underscore. SWIG does not create cvar if there are no global variables in a module.

32.3.4 Constants and enums

33.3.4 Constants and enums

@@ -1094,7 +1094,7 @@ other object. Unfortunately, there is no easy way for SWIG to generate code that prevents this. You will just have to be careful.

32.3.5 Pointers

33.3.5 Pointers

@@ -1235,7 +1235,7 @@ C-style cast may return a bogus result whereas as the C++-style cast will return None if the conversion can't be performed.

32.3.6 Structures

33.3.6 Structures

@@ -1424,7 +1424,7 @@ everything works just like you would expect. For example: -

32.3.7 C++ classes

33.3.7 C++ classes

32.3.8 C++ inheritance

33.3.8 C++ inheritance

@@ -1568,7 +1568,7 @@ then the function spam() accepts Foo * or a pointer to any cla It is safe to use multiple inheritance with SWIG.

32.3.9 Pointers, references, values, and arrays

33.3.9 Pointers, references, values, and arrays

@@ -1629,7 +1629,7 @@ treated as a returning value, and it will follow the same allocation/deallocation process.

32.3.10 C++ overloaded functions

33.3.10 C++ overloaded functions

@@ -1752,7 +1752,7 @@ first declaration takes precedence. Please refer to the "SWIG and C++" chapter for more information about overloading.

32.3.11 C++ operators

33.3.11 C++ operators

@@ -1841,7 +1841,7 @@ Also, be aware that certain operators don't map cleanly to Python. For instance overloaded assignment operators don't map to Python semantics and will be ignored.

32.3.12 C++ namespaces

33.3.12 C++ namespaces

@@ -1908,7 +1908,7 @@ utilizes thousands of small deeply nested namespaces each with identical symbol names, well, then you get what you deserve.

32.3.13 C++ templates

33.3.13 C++ templates

32.3.14 C++ Smart Pointers

33.3.14 C++ Smart Pointers

32.3.15 C++ Reference Counted Objects (ref/unref)

33.3.15 C++ Reference Counted Objects (ref/unref)

32.4 Further details on the Python class interface

33.4 Further details on the Python class interface

@@ -2203,7 +2203,7 @@ of low-level details were omitted. This section provides a brief overview of how the proxy classes work.

32.4.1 Proxy classes

33.4.1 Proxy classes

@@ -2292,7 +2292,7 @@ you can attach new Python methods to the class and you can even inherit from it by Python built-in types until Python 2.2).

32.4.2 Memory management

33.4.2 Memory management

@@ -2484,7 +2484,7 @@ It is also possible to deal with situations like this using typemaps--an advanced topic discussed later.

32.4.3 Python 2.2 and classic classes

33.4.3 Python 2.2 and classic classes

@@ -2521,7 +2521,7 @@ class itself. In Python-2.1 and earlier, they have to be accessed as a global function or through an instance (see the earlier section).

32.5 Cross language polymorphism

33.5 Cross language polymorphism

@@ -2555,7 +2555,7 @@ proxy classes, director classes, and C wrapper functions takes care of all the cross-language method routing transparently.

32.5.1 Enabling directors

33.5.1 Enabling directors

32.5.2 Director classes

33.5.2 Director classes

32.5.3 Ownership and object destruction

33.5.3 Ownership and object destruction

@@ -2797,7 +2797,7 @@ deleting all the Foo pointers it contains at some point. Note that no hard references to the Foo objects remain in Python.

32.5.4 Exception unrolling

33.5.4 Exception unrolling

@@ -2856,7 +2856,7 @@ Swig::DirectorMethodException is thrown, Python will register the exception as soon as the C wrapper function returns.

32.5.5 Overhead and code bloat

33.5.5 Overhead and code bloat

@@ -2890,7 +2890,7 @@ directive) for only those methods that are likely to be extended in Python.

32.5.6 Typemaps

33.5.6 Typemaps

32.5.7 Miscellaneous

33.5.7 Miscellaneous

32.6 Common customization features

33.6 Common customization features

@@ -2964,7 +2964,7 @@ This section describes some common SWIG features that are used to improve your the interface to an extension module.

32.6.1 C/C++ helper functions

33.6.1 C/C++ helper functions

@@ -3045,7 +3045,7 @@ hard to implement. It is possible to clean this up using Python code, typemaps, customization features as covered in later sections.

32.6.2 Adding additional Python code

33.6.2 Adding additional Python code

32.6.3 Class extension with %extend

33.6.3 Class extension with %extend

@@ -3283,7 +3283,7 @@ Vector(12,14,16) in any way---the extensions only show up in the Python interface.

32.6.4 Exception handling with %exception

33.6.4 Exception handling with %exception

@@ -3409,7 +3409,7 @@ The language-independent exception.i library file can also be used to raise exceptions. See the SWIG Library chapter.

32.7 Tips and techniques

33.7 Tips and techniques

@@ -3419,7 +3419,7 @@ strings, binary data, and arrays. This chapter discusses the common techniques solving these problems.

32.7.1 Input and output parameters

33.7.1 Input and output parameters

@@ -3632,7 +3632,7 @@ void foo(Bar *OUTPUT); may not have the intended effect since typemaps.i does not define an OUTPUT rule for Bar.

32.7.2 Simple pointers

33.7.2 Simple pointers

@@ -3701,7 +3701,7 @@ If you replace %pointer_functions() by %pointer_class(type,name)SWIG Library chapter for further details.

32 SWIG and Python

33 SWIG and Python