Re: [pygccxml-development] Feature proposal: "Argument policies"
Brought to you by:
mbaas,
roman_yakovenko
From: Roman Y. <rom...@gm...> - 2006-04-21 12:51:26
|
On 4/20/06, Niki Spahiev <ni...@vi...> wrote: > Roman Yakovenko wrote: > > I'd like to add next example, from what you can see that argument > > policies should be able to deal with more complex case: > > > > //read from some file > > int read( byte* buffer, unsigned int buffer_size ); > [...] > > Bottom line - new name needed. > > > > Suggestions: > > > > [ function ] wrapper call policies > > > > Comments? > > > > In SWIG they are called typemaps. There are input, output, exception and > some other kinds of typemaps. Thanks for input. Can you send me link to the relevant piece of documentati= on? > As SWIG is C++ parser too, IMHO most if > the issues to handle are the same. I am sure they do it. > IIRC SWIG can (or is a planing to) > save XML. Do you mean that they are going to save C++ declarations as XML in file? > Niki Spahiev > -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |