Re: [E-devel] Changing the object lifecycle - removal of eo_del, and allowing unref when there is a parent

2016-05-17 Thread Tom Hacohen
On 12/05/16 13:58, Tom Hacohen wrote: > Hey, > > This email assumes some knowledge of Eo in order to keep it short. > > > eo_del() was introduced partially as a continuation to what was in evas, > and partially as a solution to circumstances that no longer apply. In > short, it is no longer

Re: [E-devel] Changing the object lifecycle - removal of eo_del, and allowing unref when there is a parent

2016-05-13 Thread Felipe Magno de Almeida
On Thu, May 12, 2016 at 9:58 AM, Tom Hacohen wrote: > Hey, > > This email assumes some knowledge of Eo in order to keep it short. > Therefore, I suggest we just allow unreffing the last ref (the parent > one) with eo_unref() which will implicitly unparent the object as the

Re: [E-devel] Changing the object lifecycle - removal of eo_del, and allowing unref when there is a parent

2016-05-12 Thread David Seikel
On Thu, 12 May 2016 13:58:42 +0100 Tom Hacohen wrote: > Hey, > > This email assumes some knowledge of Eo in order to keep it short. > > > eo_del() was introduced partially as a continuation to what was in > evas, and partially as a solution to circumstances that no

[E-devel] Changing the object lifecycle - removal of eo_del, and allowing unref when there is a parent

2016-05-12 Thread Tom Hacohen
Hey, This email assumes some knowledge of Eo in order to keep it short. eo_del() was introduced partially as a continuation to what was in evas, and partially as a solution to circumstances that no longer apply. In short, it is no longer necessary to have eo_del() as separate from