Re: [pygccxml-development] Indexing suite exception

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

Roman Yakovenko wrote:
>> I have that already in my script, but I still get a line for each
>> individual file that is written. Maybe these messages should be debug
>> messages instead of info messages (I think a summary of the time it took
>> to write the files and maybe how many files were actually updated would
>> be enough in the standard case).
>> (But apart from that there is still a lot of output from my own script
>> that would drown the message anyway)
> 
> Do you want/have time to make pyplusplus messages really useful? Can you
> fix current situation?

I'll have a look at it when I have some time left...

>> I think it's not so much of a problem
>> that pyplusplus generated invalid code but it's more serious that I
>> missed the warnings about that (if I had seen them I wouldn't have tried
>> compiling the code in the first place).
> 
> Would it be helpful, if pyplusplus will dump the information to the
> generated source
> files, too? So when you see compilation error you also can read an 
> explanation.

So far, I wouldn't have looked into the generated source code to find 
documentation text explaining why something failed but I like the idea. 
I think it wouldn't do any harm putting some extra comments into the 
source files if pyplusplus knows in advance that a particular construct 
might cause problems in some situations.

>> default, namely the console window). My suggestion would be to write the
>> really important messages (like the max arity thing) into a separate log
>> file in addition to writing to stdout (or actually it should be stderr).
> 
> What is your definition/guide line of "really important"? Also I agree 
> with you.

As it turned out the max arity is not so important anymore as I thought 
(see my previous mail). But in general, I think the important messages 
are those that are supposed to trigger some user action (e.g. missing 
policies where a user must provide additional information to be able to 
get source code that compiles).

>> > Then he will update decl_wrappers.calldef_t.BOOST_PYTHON_MAX_ARITY 
>> to the
>> > actual number and will get rid of warning :-)
>>
>> Aha, there we are... :)
>> (though I'd recommend to add functionality to the high level API to
>> read/write this value so that the details of where the attribute is
>> actually stored in pyplusplus are encapsulated)
> 
> :-) I will add new property to module_builder_t. That is what you meant, 
> right?

Right. :)

- Matthias -