On Wed, Apr 8, 2015 at 3:37 AM, Jean-Philippe André <j...@videolan.org> wrote: > @Eo guys, > > On Wed, Apr 8, 2015 at 3:25 PM, Conrad Meyer <jp.an...@samsung.com> wrote: > >> jpeg pushed a commit to branch master. >> >> >> http://git.enlightenment.org/core/efl.git/commit/?id=0c21b91f0fe5dd61080aaba7902907837d842c26 >> >> commit 0c21b91f0fe5dd61080aaba7902907837d842c26 >> Author: Conrad Meyer <jp.an...@samsung.com> >> Date: Wed Apr 8 14:34:46 2015 +0900 >> >> Edje: Remove excessive casts and use type Edje_Object >> >> Use type Edje_Object instead of Eo in legacy EAPI's. > > > I saw lots of inconsistent type usage when going through Evas legacy > headers. > Do we want to use stronger type names? I.e.: > > Evas_Image for evas_object_image functions, > Evas_Object for generic evas_object functions, > And Eo only as a last resort? > > I spotted those in the ABI report.
I don't know about legacy. But I think the type name used should convey the most restricted set of objects where all valid types are part of this set. IOW, stronger type names. This helps C++ static type checking and will avoid unecessary downcasting on C++ and other static typing languages. I think we should make this a guideline and/or policy. Regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
