On Thu, Apr 16, 2015 at 8:25 PM, Adrien Nader <adr...@notk.org> wrote: > After discussing this a bit more on #e.fr, it occurred to me the > simplest would be to #undef EAPI at the end of headers. Basically this > turns EAPI into a header-specific define. > > The annotations (both ELF visibility and Windows dllimport/export) are > only needed on the function declaration, not on the function definition. > However we enjoy the "EAPI" in the implementation so instead it could be > defined to nothing. > > This amounts to adding the following at the end of each public header: > #undef EAPI > #define EAPI > > This shouldn't be an issue for any situation and would make sense to add > to 1.14 right now. Actually I'm joking about that: I thought it'd be > good to have people cry a bit more about the feature freeze not being > applied. :) > So, that means it'd be for the beginning of the next cycle. > > Any thought?
As part of the French cabal, I fully agree with this plan that should make a lot of include mistake be gone. I will work on that asap. -- Cedric BAIL ------------------------------------------------------------------------------ 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
