Using the above table as a guide, each target language defines a collection of "typecheck" typemaps. -The follow excerpt from the Python module illustrates this: +The following excerpt from the Python module illustrates this:
The bottom line: If you are writing new typemaps and you are using overloaded methods, you will probably -have to write typecheck code or copy existing code. Since this is a relatively new SWIG feature, there are -few examples to work with. However, you might look at some of the existing library files likes 'typemaps.i' for -a guide. +have to write new typecheck code or copy and modify existing typecheck code.
++If you write a typecheck typemap and omit the precedence level, for example commenting it out as shown below: +
+ +
+%typemap(typecheck /*,precedence=SWIG_TYPECHECK_INTEGER*/) int {
+ $1 = PyInt_Check($input) ? 1 : 0;
+}
+
++then the type is given a precedence higher than any other known precedence level and a warning is issued: +
+ ++example.i:18: Warning 467: Overloaded method foo(int) not supported (no type checking rule for 'int'). ++
Notes: