On Tue, Apr 17, 2012 at 5:01 PM, Tom Hacohen <[email protected]> wrote: > On 17/04/12 10:55, Carsten Haitzler (The Rasterman) wrote: >> i don't see the point. it's just a pointer to something. it's fine as-is. in >> this way of doing an api we no longer can use the const attribute to say >> anything about the object here. there isn't a lot of point either. > > I find it nice to have in cases where you want to query the object but > not modify it. For example, but not only: when returning textblock > cursors (assuming they were Eobj as well) from the textblock API... > > But ok, if you think it's not needed ATM I'll just wait until I find a > concrete use case.
I do disagree with raster on this. Const is a must, it help compiler and developer spot their error more easily. It also help for some optimization. I do thing that adding an eo_query(const Eo *obj, ...); is worth it. It does means that we do have a new class of function pointer in Eo. So we better think about it now, rather than later and break our structure and ABI. -- Cedric BAIL ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
