Re: [pygccxml-development] [FT] small issue

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

On 9/25/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > Because when user will try to add new transformation, he will need to
> > understand code creators
>
> Why do you think this is the case? It's not. If a transformer creates
> code that requires a particular header, it has to declare so by calling
> the require_header() method on the corresponding code manager object.

Why creator_t can not ask the code manager required headers?

> >> So how does the current design deal with the problem that a code creator
> >> might generate code that requires a particular header file?
> >
> > Very very simple - all this information creator_t takes from
> > decl_wrappers classes.
>
> Could you provide an explanation using the following example scenario:
>
> A user implements a custom code creator in his generation script. The
> code creator can be parameterized and can produce slightly different
> code depending on those parameters. Each code variation has its own set
> of required header files, some of which are written by the user, some
> are part of the project he's creating wrappers for and some might be
> from the Py++ code repository.
> After the Py++ code creator tree has been built, the user adds several
> of his custom creators at appropriate places into the tree.
>
> Now the question is, what else has to be done to include the required
> header files and who's actually including them?

User should modify the code creators tree and add "include" creators to it.
Now, how he finds out what "include"s are needed is up to him. He is free to
implement this as he wants. This is because he implements this functionality
"out of the factory".

> And where do the
> decl_wrapper classes come into play here?

decl_wrapper does not come into play here.


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