[pygccxml-development] Re: recent changes to pygccxml\pyplusplus

[Allen B. <al...@vr...>]

Roman Yakovenko wrote:

>I send this mail to mailing list, but forgot to send it to you.
>
>Please, subscribe to the mailing list and replay to mailing list
>
>Thank you
>
>On 2/28/06, Roman Yakovenko <rom...@gm...> wrote:
>  
>
>>Hi. In order to create more user friendly API I had to make few
>>changes to both projects.
>>Here is a list of changes:
>>
>>Allen changes:
>>=============
>>- Added verbose flag for additional output
>>   - pygccxml: parser (through parser config), project_reader,
>>               cache
>>      - Added timing information to output
>>      - Outputs gccxml command line
>>
>>Accepted, but in future we will replace print statemnet with logging module
>>    
>>
Sounds good.

>>=============
>>- Cache refactoring
>>
>>Accepted
>>
>>=============
>>Detection of gccxml errors
>>
>>Not accepted, it does not work with my version of gccxml, may be we
>>need to define
>>with what version of gcc xml we are working?
>>    
>>
okay.  I will check at home.  I believe I have gccxml from cvs 1 week 
old.  I am running it on Linux (FC4).

>>=============
>>- Decl Decorator
>>
>>Not accepted. I created declaration wrapper for every declaration. See
>>pyplusplus\decl_wrappers, But decorators is much better name. Should
>>we rename them?
>>    
>>
This seems like a lot of code to accomplish something that really 
amounts to having a 4-5 flags per declaration.  I can live with the 
implementation but it seems like overkill IMHO.

>>=============
>>- Additional information when finalize fails
>>
>>Not accepted. The reason is simple, I think that I don't have to
>>provide this functionality
>>on code creators at all. I will remove it. If you don't want to create
>>a wrapper you will
>>say it using standard way - customizing declarations.
>>    
>>
I don't understand what you are saying here.  How will we finalize now?  
How will the user be warned if things can't be finalized?

>>=============
>>- Extended multiple file writer
>>
>>Accepted as is.
>>
>>=============
>>Spelling fixes
>>
>>Accepted. Please fix as much as you can :-)
>>
>>=============
>>The latest versions of gccxml mark all classes and structs as artificial.
>>
>>Accepted
>>=============
>>Added/extended comments in some places
>>
>>Accepted
>>=============
>>
>>
>>My changes:
>>
>>pyplusplus:
>>
>>New classes that derives from declaration_t class.
>>Every derived decl_wrapper has relevant properties for customizing code
>>creators\module_creator.
>>
>>All code creators properties it is just an redirection to decl_wrapper
>>properties.
>>
>>pygccxml:
>>For every declaration class I am going to add *_matcher_t classes.
>>This will help
>>user to find declaration by type using some predefined criterias.
>>    
>>
Can you give some example of this?

-Allen

>>Also we should add to pygccxml all code that Allen wrote in filter.py module.
>>But it should be changed a little to use pygccxml coding convention +
>>instead of using
>>flags, I think, it should use isinstance function.
>>
>>I also added module_builder module. Please take a look on it.
>>
>>Thanks
>>
>>
>>--
>>Roman Yakovenko
>>C++ Python language binding
>>http://www.language-binding.net/
>>
>>    
>>
>
>
>--
>Roman Yakovenko
>C++ Python language binding
>http://www.language-binding.net/
>
>  
>