As described in The run-time type checker, the functions SWIG_TypeQuery, SWIG_NewPointerObj, and others sometimes need to be called. Calling these functions from a typemap is supported, since the typemap code -is embedded into the _wrap.c file, which has those declerations available. If you need +is embedded into the _wrap.c file, which has those declarations available. If you need to call the SWIG run-time functions from another C file, there is one header you need to include. To generate the header that needs to be included, run the following command: @@ -94,7 +94,7 @@ $ swig -python -external-runtime <filename> be something like swigpyrun.h, depending on the language. This header file should be treated like any of the other _wrap.c output files, and should be regenerated when the _wrap files are. After including this header, your code will be able to call SWIG_TypeQuery, -SWIG_NewPointerObj, SWIG_ConvertPtr and others. The exact argument paramaters +SWIG_NewPointerObj, SWIG_ConvertPtr and others. The exact argument parameters for these functions might differ between language modules; please check the language module chapters for more information.
@@ -104,7 +104,7 @@ need to link against the language libraries like libpython-2.3). Data is shared file and the _wrap.c files through a global variable in the scripting language. It is also possible to copy this header file along with the generated wrapper files into your own package, so that you can distribute a package that can be compiled without SWIG installed (this works -because the header file is self contained, and does not need to link with anything). +because the header file is self-contained, and does not need to link with anything).