Re: [pygccxml-development] array_t vs pointer_t
Brought to you by:
mbaas,
roman_yakovenko
From: Matthias B. <ba...@ir...> - 2006-04-11 15:47:16
|
Roman Yakovenko wrote: >> I'm wrapping a method that takes one single argument of type "double >> scale[3]". In the argument list of the corresponding declaration object >> this appears as a pointer_t object with a double_t object as base. What >> I'm missing is the '3'. >> I noticed that pyplusplus defines a type array_t. Shouldn't the above >> argument be an array_t instead of a pointer_t to a double? Is this a bug >> in pyplusplus, in gccxml or something else? > > I could be wrong, but this is how C/C++ works. Array is passed by pointers. > Am I wrong? Even if I wrong, GCC-XML reports this. That's too bad. :( The array size would have been a valuable piece of information for creating the wrappers. Without them I have to wade through ~250 methods manually to check if the arguments are really plain pointers or fixed size arrays as above (which seems to be the majority of cases in the Maya SDK)... In which case does pygccxml create an array_t object then? - Matthias - |