Thread: QT question

In the examples of QT, address book, I see this code in the AddressBook class:

Code:

    
//in class
AddressBook* ui;
QLineEdit* nameLine;

//in constructor
nameLine = new QLineEdit;
nameLine = ui->nameLine;

So my question is since nameLine points to a new object QLineEdit and then points to ui->nameLine, isn't a memory leak created?

The constructor starts

Code:

AddressBook::AddressBook(QWidget *parent)
    : QWidget(parent), ui(new Ui::AddressBook)
{
     ui->setupUi(this);

Anyway, I think it is kind of meaningless to see what QTCreator actually does.
The point is that there seems to be ne meaning for all of this, except if the example was taken from an older versiont of QT, which I believe is the case.
The whole point was that a basic object is created that is pointed by ui and we then can only play around with this. So we just link the pointer of this to the objects of the basic object pointed by ui.

If I don't allocate memory it seems to work fine.

I am quite sure it is a leak. And there is nothing that deletes the object in the destructor. But the thing is why would you ever do

Code:

pointer = new Obj;
pointer = something;

I mean, no matter what the case is, how could the above code possibly not to something weird?

They actually have two examples in there. The example I am using is the correct one, the other is how to create widgets without not graphically, but purely code-wise.

I really don't know why do they have this line of code...

qt's memory management is utter fail. it at least encourages, if not outright requires, bad practices.

that first (leaking) line would normally create a qwidget in it's own window. if you were to close the window, it would clean up after itself.

i don't understand the purpose of phrasing the code in that manner in the slightest either.