Re: [pygccxml-development] Re : Call policy for a function returning a map

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

On Wed, Jul 30, 2008 at 6:00 PM, Vincent Ferries
<vin...@gm...> wrote:
> Ok, thanks for your answear.
>
> With further investigations, I thing the cause of my problem comes
> from the non-call to the constructor when instanciating my class. Some
> variables are not initialized and then the program encounters problems
> to store datas in unreserved memory. (-> segmentations faults)
>
>
> I have the following constructor (I simpllify it a little) :
>
> dataBase::dataBase(void) : generic::dataBase() {
>   try {
>      // Just for debugging purpose
>      cout << "Here we are in constructor!" << endl;
>      properties.clear();
>   }
>   catchAll("dataBase::dataBase(void)","");
> }
>
>
> I didn't seem to go through it, the first log sentence was never printed.
> I've gone in the associated wrapper class and found this declaration
> for the constructor :
>
> struct dataBase_wrapper : postLib::nastran::dataBase, bp::wrapper<
> postLib::nastran::dataBase > {
>
>    dataBase_wrapper( )
>    : postLib::nastran::dataBase( )
>      , bp::wrapper< postLib::nastran::dataBase >(){
>        // null constructor
>
>    }
>
> It seems weird to me...
> According to me, the instanciation of the corresponding class in
> Python should instanciate the underneath class with its defined
> constructor...
>
> Is there a bug or am I missing something?

I need to see Python code

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