![](/user_photo/_userpic.png)
- •Preface
- •Introduction
- •SWIG resources
- •About this manual
- •Prerequisites
- •Organization of this manual
- •How to avoid reading the manual
- •Credits
- •What’s new?
- •Bug reports
- •SWIG is free
- •Introduction
- •What is SWIG?
- •Life before SWIG
- •Life after SWIG
- •The SWIG package
- •A SWIG example
- •The swig command
- •Building a Perl5 module
- •Building a Python module
- •Shortcuts
- •Documentation generation
- •Building libraries and modules
- •C syntax, but not a C compiler
- •Non-intrusive interface building
- •Hands off code generation
- •Event driven C programming
- •Automatic documentation generation
- •Summary
- •SWIG for Windows and Macintosh
- •SWIG on Windows 95/NT
- •SWIG on the Power Macintosh
- •Cross platform woes
- •How to survive this manual
- •Scripting Languages
- •The two language view of the world
- •How does a scripting language talk to C?
- •Wrapper functions
- •Variable linking
- •Constants
- •Structures and classes
- •Shadow classes
- •Building scripting language extensions
- •Static linking
- •Shared libraries and dynamic loading
- •Linking with shared libraries
- •SWIG Basics
- •Running SWIG
- •Input format
- •SWIG Output
- •Comments
- •C Preprocessor directives
- •SWIG Directives
- •Simple C functions, variables, and constants
- •Integers
- •Floating Point
- •Character Strings
- •Variables
- •Constants
- •Pointers and complex objects
- •Simple pointers
- •Run time pointer type checking
- •Derived types, structs, and classes
- •Typedef
- •Getting down to business
- •Passing complex datatypes by value
- •Return by value
- •Linking to complex variables
- •Arrays
- •Creating read-only variables
- •Renaming declarations
- •Overriding call by reference
- •Default/optional arguments
- •Pointers to functions
- •Typedef and structures
- •Character strings and structures
- •Array members
- •C constructors and destructors
- •Adding member functions to C structures
- •Nested structures
- •Other things to note about structures
- •C++ support
- •Supported C++ features
- •C++ example
- •Constructors and destructors
- •Member functions
- •Static members
- •Member data
- •Protection
- •Enums and constants
- •References
- •Inheritance
- •Templates
- •Renaming
- •Adding new methods
- •SWIG, C++, and the Legislation of Morality
- •The future of C++ and SWIG
- •Objective-C
- •Objective-C Example
- •Constructors and destructors
- •Instance methods
- •Class methods
- •Member data
- •Protection
- •Inheritance
- •Referring to other classes
- •Categories
- •Implementations and Protocols
- •Renaming
- •Adding new methods
- •Other issues
- •Conditional compilation
- •The #if directive
- •Code Insertion
- •The output of SWIG
- •Code blocks
- •Inlined code blocks
- •Initialization blocks
- •Wrapper code blocks
- •A general interface building strategy
- •Preparing a C program for SWIG
- •What to do with main()
- •Working with the C preprocessor
- •How to cope with C++
- •How to avoid creating the interface from hell
- •Multiple files and the SWIG library
- •The %include directive
- •The %extern directive
- •The %import directive
- •The SWIG library
- •Library example
- •Creating Library Files
- •tclsh.i
- •malloc.i
- •Static initialization of multiple modules
- •More about the SWIG library
- •Documentation System
- •Introduction
- •How it works
- •Choosing a documentation format
- •Function usage and argument names
- •Titles, sections, and subsections
- •Formatting
- •Default Formatting
- •Comment Formatting variables
- •Sorting
- •Comment placement and formatting
- •Tabs and other annoyances
- •Ignoring comments
- •C Information
- •Adding Additional Text
- •Disabling all documentation
- •An Example
- •ASCII Documentation
- •HTML Documentation
- •LaTeX Documentation
- •C++ Support
- •The Final Word?
- •Pointers, Constraints, and Typemaps
- •Introduction
- •The SWIG Pointer Library
- •Pointer Library Functions
- •A simple example
- •Creating arrays
- •Packing a data structure
- •Introduction to typemaps
- •The idea (in a nutshell)
- •Using some typemaps
- •Managing input and output parameters
- •Input Methods
- •Output Methods
- •Input/Output Methods
- •Using different names
- •Applying constraints to input values
- •Simple constraint example
- •Constraint methods
- •Applying constraints to new datatypes
- •Writing new typemaps
- •Motivations for using typemaps
- •Managing special data-types with helper functions
- •A Typemap Implementation
- •What is a typemap?
- •Creating a new typemap
- •Deleting a typemap
- •Copying a typemap
- •Typemap matching rules
- •Common typemap methods
- •Writing typemap code
- •Scope
- •Creating local variables
- •Special variables
- •Typemaps for handling arrays
- •Typemaps and the SWIG Library
- •Implementing constraints with typemaps
- •Typemap examples
- •How to break everything with a typemap
- •Typemaps and the future
- •Exception Handling
- •The %except directive
- •Handling exceptions in C code
- •Exception handling with longjmp()
- •Handling C++ exceptions
- •Using The SWIG exception library
- •Debugging and other interesting uses for %except
- •More Examples
- •SWIG and Perl5
- •Preliminaries
- •Running SWIG
- •Compiling a dynamic module
- •Building a dynamic module with MakeMaker
- •Building a static version of Perl
- •Compilation problems and compiling with C++
- •Building Perl Extensions under Windows 95/NT
- •Running SWIG from Developer Studio
- •Using NMAKE
- •Modules, packages, and classes
- •Basic Perl interface
- •Functions
- •Global variables
- •Constants
- •Pointers
- •Structures and C++ classes
- •A simple Perl example
- •Graphs
- •Sample Perl Script
- •Accessing arrays and other strange objects
- •Implementing methods in Perl
- •Shadow classes
- •Getting serious
- •Wrapping C libraries and other packages
- •Building a Perl5 interface to MATLAB
- •The MATLAB engine interface
- •Wrapping the MATLAB matrix functions
- •Putting it all together
- •Graphical Web-Statistics in Perl5
- •Handling output values (the easy way)
- •Exception handling
- •Remapping datatypes with typemaps
- •A simple typemap example
- •Perl5 typemaps
- •Typemap variables
- •Name based type conversion
- •Converting a Perl5 array to a char **
- •Using typemaps to return values
- •Accessing array structure members
- •Turning Perl references into C pointers
- •Useful functions
- •Standard typemaps
- •Pointer handling
- •Return values
- •The gory details on shadow classes
- •Module and package names
- •What gets created?
- •Object Ownership
- •Nested Objects
- •Shadow Functions
- •Inheritance
- •Iterators
- •Where to go from here?
- •SWIG and Python
- •Preliminaries
- •Running SWIG
- •Compiling a dynamic module
- •Using your module
- •Compilation problems and compiling with C++
- •Building Python Extensions under Windows 95/NT
- •Running SWIG from Developer Studio
- •Using NMAKE
- •The low-level Python/C interface
- •Modules
- •Functions
- •Variable Linking
- •Constants
- •Pointers
- •Structures
- •C++ Classes
- •Python shadow classes
- •A simple example
- •Why write shadow classes in Python?
- •Automated shadow class generation
- •Compiling modules with shadow classes
- •Where to go for more information
- •About the Examples
- •Solving a simple heat-equation
- •The C++ code
- •Making a quick and dirty Python module
- •Using our new module
- •Accessing array data
- •Use Python for control, C for performance
- •Getting even more serious about array access
- •Implementing special Python methods in C
- •Summary (so far)
- •Wrapping a C library
- •Preparing a module
- •Using the gd module
- •Building a simple 2D imaging class
- •A mathematical function plotter
- •Plotting an unstructured mesh
- •From C to SWIG to Python
- •Putting it all together
- •Merging modules
- •Using dynamic loading
- •Use static linking
- •Building large multi-module systems
- •A complete application
- •Exception handling
- •Remapping C datatypes with typemaps
- •What is a typemap?
- •Python typemaps
- •Typemap variables
- •Name based type conversion
- •Converting Python list to a char **
- •Using typemaps to return arguments
- •Mapping Python tuples into small arrays
- •Accessing array structure members
- •Useful Functions
- •Standard typemaps
- •Pointer handling
- •Implementing C callback functions in Python
- •Other odds and ends
- •Adding native Python functions to a SWIG module
- •The gory details of shadow classes
- •A simple shadow class
- •Module names
- •Two classes
- •The this pointer
- •Object ownership
- •Constructors and Destructors
- •Member data
- •Printing
- •Shadow Functions
- •Nested objects
- •Inheritance and shadow classes
- •Methods that return new objects
- •Performance concerns and hints
- •SWIG and Tcl
- •Preliminaries
- •Running SWIG
- •Additional SWIG options
- •Compiling a dynamic module (Unix)
- •Using a dynamic module
- •Static linking
- •Compilation problems
- •Using [incr Tcl] namespaces
- •Building Tcl/Tk Extensions under Windows 95/NT
- •Running SWIG from Developer Studio
- •Using NMAKE
- •Basic Tcl Interface
- •Functions
- •Global variables
- •Constants
- •Pointers
- •Structures
- •C++ Classes
- •The object oriented interface
- •Creating new objects
- •Invoking member functions
- •Deleting objects
- •Accessing member data
- •Changing member data
- •Relationship with pointers
- •About the examples
- •Binary trees in Tcl
- •Making a quick a dirty Tcl module
- •Building a C data structure in Tcl
- •Implementing methods in C
- •Building an object oriented C interface
- •Building C/C++ data structures with Tk
- •Accessing arrays
- •Building a simple OpenGL module
- •Wrapping gl.h
- •Wrapping glu.h
- •Wrapping the aux library
- •A few helper functions
- •An OpenGL package
- •Using the OpenGL module
- •Problems with the OpenGL interface
- •Exception handling
- •Typemaps
- •What is a typemap?
- •Tcl typemaps
- •Typemap variables
- •Name based type conversion
- •Converting a Tcl list to a char **
- •Remapping constants
- •Returning values in arguments
- •Mapping C structures into Tcl Lists
- •Useful functions
- •Standard typemaps
- •Pointer handling
- •Writing a main program and Tcl_AppInit()
- •Creating a new package initialization library
- •Combining Tcl/Tk Extensions
- •Limitations to this approach
- •Dynamic loading
- •Turning a SWIG module into a Tcl Package.
- •Building new kinds of Tcl interfaces (in Tcl)
- •Shadow classes
- •Extending the Tcl Netscape Plugin
- •Using the plugin
- •Tcl8.0 features
- •Advanced Topics
- •Creating multi-module packages
- •Runtime support (and potential problems)
- •Why doesn’t C++ inheritance work between modules?
- •The SWIG runtime library
- •A few dynamic loading gotchas
- •Dynamic Loading of C++ modules
- •Inside the SWIG type-checker
- •Type equivalence
- •Type casting
- •Why a name based approach?
- •Performance of the type-checker
- •Extending SWIG
- •Introduction
- •Prerequisites
- •SWIG Organization
- •The organization of this chapter
- •Compiling a SWIG extension
- •Required C++ compiler
- •Writing a main program
- •Compiling
- •SWIG output
- •The Language class (simple version)
- •A tour of SWIG datatypes
- •The DataType class
- •Function Parameters
- •The String Class
- •Hash Tables
- •The WrapperFunction class
- •Typemaps (from C)
- •The typemap C API.
- •What happens on typemap lookup?
- •How many typemaps are there?
- •File management
- •Naming Services
- •Code Generation Functions
- •Writing a Real Language Module
- •Command Line Options and Basic Initialization
- •Starting the parser
- •Emitting headers and support code
- •Setting a module name
- •Final Initialization
- •Cleanup
- •Creating Commands
- •Creating a Wrapper Function
- •Manipulating Global Variables
- •Constants
- •A Quick Intermission
- •Writing the default typemaps
- •The SWIG library and installation issues
- •C++ Processing
- •How C++ processing works
- •Language extensions
- •Hints
- •Documentation Processing
- •Documentation entries
- •Creating a usage string
- •Writing a new documentation module
- •Using a new documentation module
- •Where to go for more information
- •The Future of SWIG
- •Index
SWIG Users Guide |
Extending SWIG |
290 |
|
|
|
ments. f is a WrapperFunction object where the local variables will be created.
void emit_func_call(char *name, DataType *t, ParmList *l, WrapperFunction &f);
Creates a function call to a C function. name is the name of the C function, t is the return datatype, l is the function parameters and f is a WrapperFunction object. The code generated by this function assumes that one has first called emit_args().
void emit_banner(FILE *file);
Emits the SWIG banner comment to the output file.
void emit_set_get(char *name, char *rename, DataType *t);
Given a variable of type t, this function creates two functions to set and get the value. These functions are then wrapped like normal C functions. name is the real name of the variable. rename is the renamed version of the variable.
void emit_ptr_equivalence(FILE *file);
To keep track of datatypes, SWIG maintains an internal table of “equivalent” datatypes. This table is updated by typedef, class definitions, and other C constructs. This function emits code compatible with the type-checker that is needed to make sure pointers work correctly. Typically this function is called after an interface file has been parsed completely.
Writing a Real Language Module
Whew, assuming you’ve made it this far, we’re ready to write a real language module. In this example, we’ll develop a simple Tcl module. Tcl has been chosen because it has a relatively simple C API that is well documented and easy to understand. The module developed here is not the same as the real SWIG Tcl module (which is significantly more complicated).
The header file
We will start with the same header file as before :
//File : mylang.h
//A simple SWIG Language module
class MYLANG : public Language { private:
char *module; public :
MYLANG() {
module = 0;
};
// Virtual functions required by the SWIG parser void parse_args(int, char *argv[]);
void parse();
void create_function(char *, char *, DataType *, ParmList *); void link_variable(char *, char *, DataType *);
void declare_const(char *, char *, DataType *, char *); void initialize(void);
void headers(void); void close(void);
Version 1.1, June 24, 1997
SWIG Users Guide |
Extending SWIG |
291 |
|
|
|
void set_module(char *,char **); void create_command(char *, char *);
};
Command Line Options and Basic Initialization
Command line options are parsed using the parse_args() method :
// ------------------------------------------------------------------------
// A simple SWIG Language module
//
// ------------------------------------------------------------------------
#include "swig.h" #include "mylang.h"
static char *usage = "\ My Language Options\n\
-module name |
- Set name of module\n\n"; |
// --------------------------------------------------------------------- |
|
//MYLANG::parse_args(int argc, char *argv[])
//Parse my command line options and initialize by variables.
//---------------------------------------------------------------------
void MYLANG::parse_args(int argc, char *argv[]) { // Look for certain command line options
for (int i = 1; i < argc; i++) { if (argv[i]) {
if (strcmp(argv[i],"-module") == 0) { if (argv[i+1]) {
set_module(argv[i+1],0); mark_arg(i); mark_arg(i+1);
i++;
}else { arg_error();
}
} else if (strcmp(argv[i],"-help") == 0) { fprintf(stderr,"%s\n", usage);
}
}
}
//Set location of SWIG library strcpy(LibDir,"tcl");
//Add a symbol to the parser for conditional compilation add_symbol("SWIGTCL",0,0);
//Add typemap definitions
typemap_lang = "tcl”;
}
Parsing command line options follows the same conventions as for writing a C++ main program with one caveat. For each option that your language module parses, you need to call the function mark_arg(). This tells the SWIG main program that your module found a valid option
Version 1.1, June 24, 1997
SWIG Users Guide |
Extending SWIG |
292 |
|
|
|
and used it. If you don’t do this, SWIG will exit with an error message about unrecognized command line options.
After processing command line options, you next need to set the variable LibDir with the name of the subdirectory your language will use to find files in the SWIG library. Since we are making a new Tcl module, we’ll just set this to “tcl”.
Next, we may want to add a symbol to SWIG’s symbol table. In this case we’re adding “SWIGTCL” to indicate that we’re using Tcl. SWIG modules can use this for conditional compilation and detecting your module using #ifdef.
Finally, we need to set the variable typemap_lang. This should be assigned a name that you would like to use for all typemap declarations. When a user gives a typemap, they would use this name as the target language.
Starting the parser
To start the SWIG parser, the parse() method is used :
// ---------------------------------------------------------------------
//void MYLANG::parse()
//Start parsing an interface file for MYLANG.
//---------------------------------------------------------------------
void MYLANG::parse() {
fprintf(stderr,"Making wrappers |
for Tcl\n"); |
|
headers(); |
// Emit header |
files and other supporting code |
// Tell the parser to first include a typemap definition file
if (include_file("lang.map") == -1) { fprintf(stderr,"Unable to find lang.map!\n"); SWIG_exit(1);
} |
|
yyparse(); |
// Run the SWIG parser |
}
This function should print some kind of message to the user indicating what language is being targeted. The headers() method is called (see below) to emit support code and header files. Finally, we make a call to yyparse(). This starts the SWIG parser and does not return until the entire interface file has been read.
In our implementation, we have also added code to immediately include a file ‘lang.map’. This file will contain typemap definitions to be used by our module and is described in detail later.
Emitting headers and support code
Prior to emitting any code, our module should emit standard header files and support code. This is done using the headers() method :
// ---------------------------------------------------------------------
// MYLANG::headers(void)
//
Version 1.1, June 24, 1997
SWIG Users Guide |
Extending SWIG |
293 |
|
|
|
//Generate the appropriate header files for MYLANG interface.
//----------------------------------------------------------------------
void MYLANG::headers(void)
{
emit_banner(f_header); // Print the SWIG banner message fprintf(f_header,"/* Implementation : My TCL */\n\n");
//Include header file code fragment into the output if (insert_file("header.swg",f_header) == -1) {
fprintf(stderr,"Fatal Error. Unable to locate 'header.swg'.\n"); SWIG_exit(1);
}
//Emit the default SWIG pointer type-checker (for strings)
if (insert_file("swigptr.swg",f_header) == -1) { fprintf(stderr,"Fatal Error. Unable to locate 'swigptr.swg'.\n"); SWIG_exit(1);
}
}
In this implementation, we emit the standard SWIG banner followed by a comment indicating which language module is being used. After that, we are going to include two different files. ‘header.swg’ is a file containing standard declarations needed to build a Tcl extension. For our example, it will look like this :
/* File : header.swg */ #include <tcl.h>
The file ‘swigptr.swg’ contains the standard SWIG pointer-type checking library. This library contains about 300 lines of rather nasty looking support code that define the following 3 functions :
void SWIG_RegisterMapping(char *type1, char *type, void *(*cast)(void *))
Creates a mapping between C datatypes type1 and type2. This is registered with the runtime type-checker and is similiar to a typedef. cast is an optional function pointer defining a method for proper pointer conversion (if needed). Normally, cast is only used when converting between base and derived classes in C++ and is needed for proper implementation of multiple inheritance.
void SWIG_MakePtr(char *str, void *ptr, char *type);
Makes a string representation of a C pointer. The result is stored in str which is assumed to be large enough to hold the result. ptr contains the pointer value and type is a string code corresponding to the datatype.
char *SWIG_GetPtr(char *str, void **ptr, char *type);
Extracts a pointer from its string representation, performs type-checking, and casting. str is the string containing the pointer-value representation, ptr is the address of the pointer that will be returned, and type is the string code corresponding to the datatype. If a type-error occurs, the function returns a char * corresponding to the part of the input string that was invalid, otherwise the function returns NULL. If a NULL pointer is given for type, the function will accept a pointer of any type.
Version 1.1, June 24, 1997