Hi all, This morning, I pushed the Eo pointers indirection feature. As I wrote in the log, it is not API break. It will help us against bad usage of Eo objects pointers, e.g access an object that has already been deleted... So if you see that the Eo* that you receive from eo_add doesn't seem like a "normal" pointer, but like 0x1000401, just know it is normal. If you need a better explanation on the mechanism used, check the file eo_ptr_indirection.c in src/lib/eo.
If you see error messages "obj_id ... is not pointing to a valid object. Maybe it has already been freed.", check your Eo objects or contact me. Enjoy JackDanielZ ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
