Let me know your valid suggession for Memory Leak ..!!!

[joseph]

So i need not be worried of the MEMORY LEAK....
I did not mean that Qt will break the promises, instead just want to know your suggessions as you people are more experienced than me.

Thank you wysota

[wysota]

It's written in the docs more than a dozen times that Qt takes responsibility over items which have a parent set.

[sunil.thaha]

And to add to what wysota had said
It is a good practice to create that QTable on heap rather than declare it as QTable table;

[joseph]

sunil,

Actually m_table is in heap itself .Its my mistake that i didn't mentioned like this..

class MyMainWindow : QMainWindow
{
          -------
         --------
 
public :
        QTable * m_table ;
 
 
};

class MyMainWindow : QMainWindow
{
          -------
         --------

public :
        QTable * m_table ;


};

To copy to clipboard, switch view to plain text mode 

In runtime i will call this as follows...

// m_table will be lively when the MyMainWindow is beeing created.
 m_table =  new Qtable( ...,... );

// m_table will be lively when the MyMainWindow is beeing created.
 m_table =  new Qtable( ...,... );

To copy to clipboard, switch view to plain text mode 

As Wysota told got the solution ,like m_table will be killed by the MyMainWindow , just before it's beeing killed

Thank you sunil.