On 05/09/13 17:42, Gustavo Sverzut Barbieri wrote: > Hi all, > > Why eo_del() doesn't flag the object as deleted and issue an event callback?
Because the object might still be referenced. It could be done though, we haven't decided one way or the other, this might be a reasonable approach as well. I'll think about it, as this approach also has its merits. This however does not mean that the object will be completely deleted. We'll may call the destructors, and even block eo_do, but we will not free the objects. > > As it is I feel it is pretty useless, you do the "del", it becomes > unparented and unrefs, but other than that no users will know they > should release their references... and you can keep calling object > methods without problems. They should know that in eo land, you have references, and you need to account for them. See what I wrote above. > > Could we change this behavior to flag as del? Eventually make eo_do() > fail? or at least provide a eo_deleted_check() so we can easily check > in our methods before we execute further? Also call EO_EV_DEL right > there. > Again, reasonable, I'll give it some more thought. Feel free to write what you think the pros/cons here. I do wish other people will voice their opinion as well, as this is a major change. -- Tom. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
