Clearer warning message for badly constructed typecheck typemaps
This commit is contained in:
parent
4010d25b91
commit
55e7264d43
7 changed files with 24 additions and 12 deletions
|
|
@ -492,7 +492,7 @@ example.i(4) : Syntax error in input(1).
|
|||
<li>464. Unsupported constant value.
|
||||
<li>465. Unable to handle type <em>type</em>.
|
||||
<li>466. Unsupported variable type <em>type</em>.
|
||||
<li>467. Overloaded <em>declaration</em> not supported (no type checking rule for '<em>type</em>')
|
||||
<li>467. Overloaded <em>declaration</em> not supported (incomplete type checking rule - no precedence level in typecheck typemap for '<em>type</em>')
|
||||
<li>468. No 'throw' typemap defined for exception type <em>type</em>
|
||||
<li>469. No or improper directorin typemap defined for <em>type</em>
|
||||
<li>470. Thread/reentrant unsafe wrapping, consider returning by value instead.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue