Hello, On Fri, Oct 11, 2013 at 2:03 AM, Felipe Magno de Almeida <felipe.m.alme...@gmail.com> wrote: > Currently, writing modules for enlightenment using C++ is not possible > without modifying headers from enlightenment. > > How is the policy for these headers w.r.t C++ compatibility? > > The most common problems are: > * Lack of extern "C"; > * The use of C++ keywords, e.g., class (replaced for klass); > * Functions and macros defined in the header with implicit conversion > from unrelated pointer types; > * Typedefs before definition or declaration of the typedef'ed UDT.
I think there was no real review and attempt to make Enlightenment a public stable API. I think there is already ABI/API break between E17 and E18 (and also possibly E19). So I do think that just fixing all mistake is an acceptable policy at this stage (basically patch welcome). Regards, -- Cedric BAIL ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
