Re: [pygccxml-development] Indexing suite exception

[Roman Y. <rom...@gm...>]

On 6/20/06, Matthias Baas <ba...@ir...> wrote:
> Ah, I see. Sorry, actually there was that warning message but it got
> drowned in the output, so I didn't notice it.

I am aware of the this problem ( lot of output ), so next code will
write only important
things:

import logging
from pyplusplus import module_builder
module_builder.set_logger_level( logging.INFO )


> 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?

Now when you have bad experience( and I am sorry for that ) you can
give an advice.
In my opinion pyplusplus did the job, but of  course I could be wrong.

> In the code the maximum number (10) is hard-coded, shouldn't that be at
> least be user-settable

Yes, I fixed and committed.

> (or, if possible, automatically determined).

It does not worth that, too much work ( make files, auto
configuration, scons, bjam, prj .... )

> What
> if the user actually did increase BOOST_PYTHON_MAX_ARITY?

Then he will update decl_wrappers.calldef_t.BOOST_PYTHON_MAX_ARITY to the
actual number and will get rid of warning :-)

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/