views:

80

answers:

3

What are the lifetimes of Qt Objects?

Such as:

QTcpSocket *socket=new QTcpSocket();

When socket will be destroyed? Should I use

delete socket;

Is there any difference with:

QTcpSocket socket;

I couldn't find deep infromation about this, any comment or link is welcomed.

+7  A: 

Objects allocated with new must be released with delete.

However, with Qt, most objects can have a parent, which you specify as an argument to the constructor. When the parent is deleted, the child objects get deleted automatically.

Alexandre C.
When try delete, I get runtime error (about trial to access private member in QHostAddress)
metdos
private member access isn't checked at runtime, only during compilation. Maybe it's a crash? Then your object is probably deleted twice.
Frank
+3  A: 

Qt uses parent-child relationships to manage memory. If you provide the QTcpSocket object with a parent when you create it, the parent will take care of cleaning it up. The parent can be, for example, the GUI window that uses the socket. Once the window dies (i.e. is closed) the socket dies.

You can do without the parent but then indeed you have to delete the object manually.

Personally I recommend sticking to idiomatic Qt and using linking all objects into parent-child trees.

Eli Bendersky
+2  A: 

If you don't want to pass a parent for some reason (because there is no QObject where it makes sense to own the socket object), you can also use a QSharedPointer to manage the lifetime.

Frank