Re: [pygccxml-development] How to get back an "emergency API"?

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

Roman Yakovenko wrote:
>> ok, at least the script runs without errors again. But I do get an error
>> during compilation but that's another thing now that I first have to
>> investigate...(it seems my call policies don't get assigned anymore, but
>> that's ok for now).
> 
> The only thing that I can say is that "it works fine for me". Could
> you investigate the
> problem. If this is a problem in pyplusplus you can commit the fix.

ok (but I think this could just as well be a problem in my old API which 
just has to be updated to the new version of pyplusplus. So far, I'm 
happy that I don't get an exception anymore. :)

>> I think now that pyplusplus relies on seeing its own declaration
>> classes, it would be useful to introduce a parse() function in
>> pyplusplus (which would use the dwfactory_t class as default instead of
>> the factory from pygccxml). At the moment, *every* user of pyplusplus
>> would have to pass dwfactory_t explicitly whereas this is rather an
>> implementation detail.
> 
> Yes and this is exactly the details that will be hidden in Allen class :-)

Oh, ok, but just because we will have a high level API doesn't mean we 
should be "sloppy" and introduce awkward things into the low level API. 
In my opinion, the low level API should still be kept clean and logical 
and also as "easy to use" as possible (without having to introduce new 
concepts that the high level API might already do). Maybe there are 
cases where users have to go back to the low level API for whatever 
reasons...

- Matthias -