Re: warnings when using directors with multiple throw specifiers

On 2004.05.30 14:44, Oren Miller wrote:
> FYI, I discovered the SWIG_TypeCheck, TypeCast etc. etc. methods.  It  
> seems I should be using these so I'm going to try to do so.  I was  
> unable to find any documentation on these methods however.  Are these  
> safe to use and if so is there anywhere that describes their proper  
> use?  I only discovered them when I was looking to see what  
> SWIG_ConvertPtr was doing.

http://www.swig.org/Doc1.3/Typemaps.html#n42 has a basic explination,  
but nothing about TypeCheck and TypeCast

I have made some modifications to the type system, and have a little  
better documentation available here...
http://www.cs.wisc.edu/~lenz/swig.html

When reading that site, just remember that the current SWIG type system  
does not have a swig_module_info structure and that the swig_type_info  
and swig_cast_info structures are actually one big structure that gets  
used for two different purposes.

The TypeCheck and TypeCast functions are mainly to deal with the  
problem of multiple inheritance.  Each type in the type system stores a  
linked list of types which are eqivelent to it.  TypeCheck will walk  
along this linked list, checking if the two types are equivelent.

If TypeCheck finds a match, then TypeCast should be called. TypeCast  
should be called with the return value from TypeCheck.  TypeCast deals  
with the problem of multiple inheritance, that is, it makes sure the  
pointer is pointing at the base of the object.

John
_______________________________________________
Swig maillist  -  Swig@xxxxxxxxxxxxxxx
http://mailman.cs.uchicago.edu/mailman/listinfo/swig