Re: [pygccxml-development] Indexing suite exception

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> On 6/19/06, Matthias Baas <ba...@ir...> wrote:
>>
>> So what is wrong with this method? (are there too many arguments? are
>> there some required policies missing?)
>> And another question is why was this ignored in previous versions? Which
>> modification of pyplusplus has changed that?
> 
> This should explain to you:
> 
> http://svn.sourceforge.net/viewcvs.cgi/pygccxml/pyplusplus_dev/pyplusplus/decl_wrappers/calldef_wrapper.py?r1=195&r2=214 

Ah, I see. Sorry, actually there was that warning message but it got 
drowned in the output, so I didn't notice it.

But as pyplusplus already knows that a particular member won't compile, 
shouldn't it then refuse to write it to the output file (as it was the 
case before)? Or even abort or something so that the user definitely 
knows that some action is required on his side?

In the code the maximum number (10) is hard-coded, shouldn't that be at 
least be user-settable (or, if possible, automatically determined). What 
if the user actually did increase BOOST_PYTHON_MAX_ARITY?

- Matthias -