[C++-sig] Pyste,Py++: equivalent of swig typemaps?

Hello, due to limitations of swig I am currently learning Py++ and Pyste (because it seems currently to be better documented than Py++). Does Pyste or Py++ offer typemaps like swig (http://www.swig.org/Doc1.3/SWIGDocumentation.html#Python_nn53) that allow any sequence of input arguments to be wrap

Re: [C++-sig] Pyste,Py++: equivalent of swig typemaps?

Mihail Konstantinov wrote: Hello, due to limitations of swig I am currently learning Py++ and Pyste (because it seems currently to be better documented than Py++). Does Pyste or Py++ offer typemaps like swig (http://www.swig.org/Doc1.3/SWIGDocumentation.html#Python_nn53) that allow any seque

Re: [C++-sig] [pygccxml-development] Pyste, Py++: equivalent of swig typemaps?

On Sun, Nov 30, 2008 at 8:58 PM, Mihail Konstantinov <[EMAIL PROTECTED]> wrote: > Hello, > due to limitations of swig I am currently learning Py++ and Pyste (because > it seems currently to be better documented than Py++). Hmm. Did you see http://language-binding.net/pyplusplus/pyplusplus.html pag

Re: [C++-sig] Pyste,Py++: equivalent of swig typemaps?

Thank you Stefan, the typemaps are required, when C++ functions are wrapped that expect arguments which have no direct corresponding type in python, or when standard types have to be interpreted differently. For example a function void parse_args(int argc, char **argv), which I want to call in

Re: [C++-sig] Pyste,Py++: equivalent of swig typemaps?

Mihail Konstantinov wrote: Thank you Stefan, the typemaps are required, when C++ functions are wrapped that expect arguments which have no direct corresponding type in python, or when standard types have to be interpreted differently. For example a function void parse_args(int argc, char **arg

Re: [C++-sig] Pyste,Py++: equivalent of swig typemaps?

On Sun, Nov 30, 2008 at 10:56 PM, Stefan Seefeld <[EMAIL PROTECTED]> wrote: > Mihail Konstantinov wrote: >> >> Thank you Stefan, >> the typemaps are required, when C++ functions are wrapped that expect >> arguments which have no direct corresponding type in python, or when >> standard types have to

Re: [C++-sig] Pyste,Py++: equivalent of swig typemaps?

> If I understand right SWIG feature, it allows you to define something > like "call policy" which is invoked before and after function > invocation, and it also allows you to define complex mapping between > Python and C++ arguments. So you can define it once, and then apply it > when needed. Yes