On Mon, Jun 13, 2016 at 11:11 AM, Tom Hacohen <t...@osg.samsung.com> wrote: > On 13/06/16 15:01, Stefan Schmidt wrote:
[snip] >> If you are not the author of one of these above but still think they >> should not be part of our API from 1.18 on please speak up now! >> >> I will start to gradually remove the EFL_EO_API_SUPPORT flag from our >> code base over the next days. > > I guess we'll have to do it selectively then, because only the "efl*" > APIs should be there. Any leftovers should either be internal (not > installed) or not exist. I have a problem with C++ bindings that some public classes inherit from non-public classes that should not be installed. However, for C++ we just inherit from each other in the generated binding and the files need to be available to compile. We need to either 1. remove mentioning non-public classes in public classes, or 2. have a way to tag that a class is private and should not appear in the generated inheritance tree. What do you think? > -- > Tom Regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
