Re: [pygccxml-development] Indexing suite exception

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

Lakin Wecker wrote:
>> information is passed to the user. I think it's not so much of a problem
>> that pyplusplus generated invalid code
> 
> I know that I'm just arguing semantics, but I disagree.  The code
> _does_ compile and is therefore _not_ invalid.  It just requires you
> to pass an extra switch the compiler, in this case:
> -DBOOST_PYTHON_MAX_ARITY=19 or somesuch.

Oops, I just noticed I misunderstood the whole thing. I thought I had to 
set the max arity when compiling *Boost.Python* instead of my own code.
Now that I know I have to set this when compiling my own module, it's 
not so much of an issue anymore. And yes, the code generated by 
pyplusplus is not invalid in this case.
But as you suggested, there could be an option so that pyplusplus just 
puts the appropriate #define right inside the file.

> I don't mind the current behavior as it would be easy for the user to
> hook into the logging module and write out messages above a certain
> importance to a separate log file.

Right, but why should I do that if I don't suspect any problems in the 
first place? My point is just that it always makes sense to dump serious 
error messages into a file for later inspection, so why not make this 
the default behavior? But that's only a minor issue, it's more important 
that pyplusplus internally categorizes its messages properly so that the 
user can filter out what is interesting to him.

> However, having a some sort of summary printed at the end of all the
> interesting things that a User may have to take care of would be nice.

Agreed.

- Matthias -