On Sun, 15 Apr 2012 15:34:09 +0300 Tom Hacohen <tom.haco...@samsung.com> said:
> On 13/04/12 14:02, Carsten Haitzler (The Rasterman) wrote: > > 15. eobj_generic_data_* ... i really think this should support passing in a > > free func for generic data (NULL == dont free it), and previous egenric > > data is auto-greed if u set new data on top, same when u del - dont bother > > returning the pointer to it except on get. ALSO for generic data - can u > > provide a TYPE param - string, opque, eobj, opaque list, object list etc. > > types. opaque is unknown to eobj, but string can be used to account for > > memory objects and eobj can be used to have eobj auto unref attached > > generic data if its another eobj or list of eobj's. this would come it very > > handy. > > I thought about it, but it felt a bit fat to me... The problem is that > we'd have to save a free function/NULL for every property which is kinda > wasteful. Especially since you can in most cases just have a delete > callback and free the properties from there. If you really think it's a > must, I'll add it. i'm coming back to this. i really still think we should have a free func. if it's null, nothing is freed for u. if not null it's called on object delete for any remaining properties still there. cost is just 1 more ptr. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
