File: README

package info (click to toggle)
swig 1.1p5-1
  • links: PTS
  • area: main
  • in suites: hamm
  • size: 9,448 kB
  • ctags: 5,025
  • sloc: cpp: 21,599; ansic: 13,333; yacc: 3,297; python: 2,794; makefile: 2,197; perl: 1,984; tcl: 1,583; sh: 736; lisp: 201; objc: 143
file content (33 lines) | stat: -rw-r--r-- 1,037 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
** Disclaimer **
This example demonstrates some of the more advanced features
of SWIG--don't say I didn't warn you!

In this example, we've built a simple C++ widget for making
2D plots.   The widget is really just a wrapper around some
functions in the gd-1.2 library (for simplicity). However,
the C++ widget relies on callback functions written in
C++.   To work around this problem, this example illustrates
how to :

1.  Implement a C/C++ callback function in Python
    (without C/C++ knowing about it).

2.  Use of SWIG typemaps to allow a Python
    callable object to be passed in as a function
    argument as well as mapping Python file objects into
    the FILE * datatype.

3.  Adding new methods to a C++ class.

More details about this can be found in the SWIG user's manual.


Notes :

'make ccode' builds a C++ only implementation where our
"widget" is used from a simple C++ program.

'make' or 'make static' builds a Python implementation
that uses the same C++ widget, but with callback functions
written in Python.