+This example illustrates a couple of techniques for handling +simple pointers in SWIG. The prototypical example is a C function +that operates on pointers such as this: + +
+
+void add(int *x, int *y, int *r) {
+ *r = *x + *y;
+}
+
+
+
+By default, SWIG wraps this function exactly as specified and creates
+an interface that expects pointer objects for arguments. The only
+problem is how does one go about creating these objects from a script?
+
+
+
+int *new_int(int ivalue) {
+ int *i = (int *) malloc(sizeof(ivalue));
+ *i = ivalue;
+ return i;
+}
+int get_int(int *i) {
+ return *i;
+}
+
+void delete_int(int *i) {
+ free(i);
+}
+
+
+
+Now, in a script you would do this:
+
+++ ++set a [new_int 37] +set b [new_int 42] +set c [new_int 0] +add $a $b $c +set r [get_int $c] +print "Result = $r" +delete_int $a +delete_int $b +delete_int $c ++
+
++ +The advantage to using the pointer library is that it unifies some of the helper +functions behind a common set of names. For example, the same set of functions work +with int, double, float, and other fundamental types. + ++%include "pointer.i" ++ ++set a [ptrcreate int 37] +set b [ptrcreate int 42] +set c [ptrcreate int] +add $a $b $c +set r [ptrvalue $c] +print "Result = $r" +ptrfree $a +ptrfree $b +ptrfree $c ++
+
++ +And in a script: + ++%include "typemaps.i" +void add(int *INPUT, int *INPUT, int *OUTPUT); ++
++Needless to say, this is substantially easier. + ++set r [add 37 42] +puts "Result = $r" ++
+
+
+%include "typemaps.i"
+%apply int *INPUT {int *x, int *y};
+%apply int *OUTPUT {int *r};
+
+void add(int *x, int *y, int *r);
+void sub(int *x, int *y, int *r);
+void mul(int *x, int *y, int *r);
+... etc ...
+
+
+
++
+