[pygccxml-development] FT - open issues

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

Hi. I think Py++ accumulated enough changes, so we can start on
preparing it to be released. Before we do this, I prefer to see few
issues fixed in FT:

1. Better formatting of generated code.
2. Name uniqueness\resolution. For example:
    for next C++ code

    namespace ft{
    struct xxx_t{
        static void get_value( int& x ){ x = 21; }
     private:
        ~xxx_t(){}
     };

   Py++ generates next code

   static boost::python::object _py_get_value(  ) {
       int x;
       xxx_t::get_value(x);
       return boost::python::object(x);
   }

   Obviously if I will introduce similar class with other name, Py++
will not generate
   unique name for get_value.

3. transformers index argument from 1 and not from zero. I think we
need to discuss
    this one more time. I don't agree with this interface. This is
tooooo confusing.

4. Base class for all transformations should be introduced.

5. Class that represents "final" transformation should be introduced.

6. Generated code should be different. I mean we should introduce more
convenience
    functions in code repository.

I can help with 4,5,6 items.

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