Bug free programming with Qt:

[Panke]

bq. (+ impossible to crash even if bad coded ?)

That your program does not crash, does not mean it has no bugs :-)

I agree to the other points though and think that the memory management things are most useful.

[laurent bauer]

What do you mean with "memory management things" ? The shared classes ?

[Panke]

[quote author="laurent bauer" date="1293645469"]

• Implicit sharing and associated objects with reference counting
  [/quote]

yes

[laurent bauer]

In the first post, i wrote: "You create an orphan widget, you attach it later to a parent widget. The parent takes ownership and you don’t need to worry anymore about the child life cycle"

I like this idea : you transfer the management of an object to an object owner. And you don't have to manage it yourself .

Do you know if this is a concept, a design pattern or anything which has a name?
Do you know if this coding way is described somewhere?

[giesbert]

The parent - child relationship, that includes lifetime coupling?

I would say it's a normal Komposition (UML :-) ).

[laurent bauer]

So simple? Well, I feel a bit ridiculous...

[giesbert]

Must everything be complicated?

[ivan]

In a sense, it is just an extension to the standard C++ behaviour to work with pointers (free on destruction) so it is not really a new concept.

[laurent bauer]

OK, I guess a widget has a container of children widgets which are destroyed by the parent destructor.
However, it must be a little bit more tricky because the ownership can be transfered to another parent widget.

[goetz]

It's only a QObjectList (which is just a typedef for QList<QObject *>). It is only little more than removing from one and inserting into the other list (and handling layout issues in case of widgets).

[CreMindES]

Yes, it's that simple :) The best things are so simple :)