Re: [pygccxml-development] array_t vs pointer_t
Brought to you by:
mbaas,
roman_yakovenko
From: Roman Y. <rom...@gm...> - 2006-04-20 16:38:19
|
On 4/20/06, Matthias Baas <ba...@ir...> wrote: > > An other way to solve this issue is to create small parser, that will p= arse all > > header files and will create table with relevant information. Then you > > can just use > > that information from your script. I glad you found this solution simple and useful. > I took this route and meanwhile I've implemented it. So obtaining the > array size is no problem anymore and I could assign argument policies > automatically to most methods. Those are good news. But as for me, the better news is that you did it using some custom program and then share this knowledge with code generator= . This is really grate. This was one of my goals. > Now I have the problem that the argument policy mechanism sometimes > produces wrapper methods that are ambiguous. Looks like I have to > improve my prototype so that it recognizes these cases and asks for user > help. Can you post example in relevant thread? ( Where we discuss the feature ). > But at least obtaining the array size (what this thread was actually > about) works fine. > By the way, maybe this code might be useful to some users at some point, > so I think it might be worth sharing eventually. But I don't think it's > really general and stable enough to be part of the official pyplusplus > package, so how about adding a "contrib" directory when the code is > moved to svn (maybe pyplusplus_dev/contrib) where contributions from > users could be put that is not "good enough" yet for the official > package but that might still be useful to the community either as an > example for something or as a basis for tailoring it to their own > projects? This will be code that does not have to be maintained or > supported by yourself (Roman) but users have the option to use it "at > their own risk". > Such a scheme is used by ODE (Open Dynamics Engine) and only > occasionally is code from contrib moved to the main branch when it > proves to be useful and becomes stable. Go ahead. I like this idea. I saw it in docutils. > - Matthias - -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |