To use or not to use: deleteLater()

[dpimka]

deleteLater() can delete your object at any time. You ask qt that you do not need the object and qt can delete it anytime(may be instantly)..

Hmm, I thought that deleteLater() always deletes object on next event loop iteration, so it never happens "instantly" after being issued. Or am I wrong?

[codeslicer]

Hmm, I thought that deleteLater() always deletes object on next event loop iteration, so it never happens "instantly" after being issued. Or am I wrong?

deleteLater() can delete your object at any time when the event loop has control, sometimes that can be instantly if there aren't any other events.

[nish]

deleteLater() can delete your object at any time when the event loop has control, sometimes that can be instantly if there aren't any other events.

looks like you learn very fast

So does that mean it's better to make "new" objects because those can be deleted? Or only reserve smaller objects (like bool and int) for the stack?

this is a tricky question.
in qt any class which is derived from qobject can have children(fox example a QDialog containg Ok,Cancel button as its children). Now when the qdialog is deleted, it also deletes all its children,,, if the children are on stack that will cause crash. So all the QObjects derived classes which will become child of any object in your program should be on heap.

but this is not general rule. many times a local child widget is created on stack(for example a temporary messagebox)