Hey,

As promised, these are my ABI reports. There's a bit of noise because of 
the switch to Eo2 and the fact that our object's Eo API is not always 
ifdefed out in the headers (the Eo api is though, so they can't be used 
without the define). Also, obviously, the symbols exposed in the binary 
that can not be turned off. I think though, that it's easy enough to 
scan through the noise and find the issues.

Here's the new index for all the scans:
http://enlightenment.org/~tasn/abi/

I should probably make it a table or something, don't know.

Please have a look and share if you see anything suspicious.

A good example would be:
  [+] elm_widget_focus_highlight_geometry_get ( Evas_Object const* obj, 
Evas_Coord* x, Evas_Coord* y, Evas_Coord* w, Evas_Coord* h ) (1)

But I guess that's "fine" because it's internal.

--
Tom.




------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to