wxruby users - Aug 2006 - Typemap simplification

One way we might simplify our lives is to modify the .h files so
they''re
SWIG friendly.  I think I mentioned this before but I''ll bring it up
again.

Take the following for example:

    void MyFunc( int *x, int *y ) const

You can''t tell looking at this function whether x and y are inputs, 
outputs or both (Well, you might can assume they''re not input only). 
If
we slightly modify the header files:

    void MyFunc( int *INOUTx, int *INOUTy ) const

Then it''s really obvious -and- we can make a typemap that sucks those
up
easily.

The real bear for us is when two functions in a header file treat the 
pointers differently:

    void MyFunc( int * x, int * y ) const   // In/Out
    void MyFunc2( int *x, int *y ) const   // Out only

These two would be about impossible to wrap using our current SWIG 
knowledge.  The other alternative is to put SWIG directives directly 
into the .h files.

Thoughts?

Roy

On Sat, 2006-08-26 at 00:49 -0400, Roy Sutton wrote:
>     void MyFunc( int *INOUTx, int *INOUTy ) const
> 
> Then it''s really obvious -and- we can make a typemap that sucks
those up
> easily.
True. Ugly but clear. Of course, we don''t actually care about (int*)
parameters, but your point is valid for all kinds of objects.
> The real bear for us is when two functions in a header file treat the 
> pointers differently:
> 
>     void MyFunc( int * x, int * y ) const   // In/Out
>     void MyFunc2( int *x, int *y ) const   // Out only
> 
> These two would be about impossible to wrap using our current SWIG 
> knowledge.  
You didn''t actually say it, but I believe what you are saying is that
if
we did the renaming you propose above, then we could handle those cases
easily.
> The other alternative is to put SWIG directives directly 
> into the .h files.
I had hoped to keep the .h files "pure", but I have to keep in mind my
motivations for doing so: To make them reusable by other wx wrapping
projects who use swig. By that logic, if we put all the
non-language-specific swig stuff in the .h files, it would make it
easier for other projects.


I guess I would like to try a non-trivial .h file or two, using a couple
different approaches to see which feels better.

Kevin