Re: [Fwd: [pygccxml-development] Updated status]

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

On 3/6/06, Allen Bierbaum <al...@vr...> wrote:
> A apologize in advance, this e-mail is going to be a little random
> because it is based on my notes from this afternoon.  I started trying
> to move the pypp_api interface over the the new codebase and these are
> the things I have run into right away.
>
> - Calling parser changed a bit.
>
> There seems to be a new interface to calling the project parser.  I
> think I just need to add a decl wrapper factory but I am not for sure.
> Roman?

Yes

> - How am I supposed to use the decl_wrappers?
>
> I am trying to parse with the project reader and then I was expecting
> that the returned decls would actually be the wrappers/decorators for
> the decls.  Is this how it is supposed to work?

Yes.

> - Code complexity: The new decorators does look like a LOT of additional
> code for what could be done with some grafted flags.  Not really a
> question, more of a comment.  I really think the codebase could be
> simplified a lot.  For me at least all the property usage seems like a
> lot of extra code to read through and maintain for very little payoff.

I will explain this on Wiki

> - What is module_builder_t for?  Do I have to use it?  It looks like
> Roman's stab at the higher-level interface but what do I need to copy
> from there into pypp_api.

Nothing, it exists for testers only as temporal solution.

> - Why did call policies move to the wrapper module?  Those still seem
> like code_creators.

Short answer: because when user thinks about call policies he does not thin=
k
about code generation. In future I will remove "code generation
functionality" from
call policies.

> - Decl wrappers don't seem to support everything I needed/added with the
> decorators.
>
> Specifically, how can I add custom creators?  In my flag-based version I
> could add a list of code creators that would automatically be added on
> when the creator class build the code creators for a decl.

First of all I missed this future. Sorry. I will add the functionality
to decl wrappers.

> - What are all the options that have been added to the wrappers? (see
> documentation below)

I will try to add documentation to all options wrappers have.

> - I think Logger should probably use info() for most of the current
> output.  Why put time and level name in log output?

Cut & paste. In one of my projects I had logging configuration code.
I will change it to what you proposed.

> My original goal with this output was to have verbose output for users
> not to provide a debug log to a log file on errors. Any objections to
> making the output look cleaner by making the info() filter just output
> the text instead of all the header information?

No. I will do that.

> - Comments: We *really* need comments and documentation for the classes
> and methods in pygccxml and pyplusplus.  I think Matthias and I could
> help out by pointing to areas of the code and saying in our very nicest
> voice "Roman, please please document this".

Huston, you've got a problem :-). For me it is a huge effort to write
documentation.
I can not explain my self clearly. If you don't mind, I prefer to
answer 1000 question from
you and Matthias, but you will write documentation. Please, please, please =
:-)

> That is about all I have for now.  Until I find out more about the
> decl_wrapper's and their use I am at a stand still. :(

Hope, I helped

> Thanks,
> Allen

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