On Tue, Aug 16, 2016 at 3:37 PM, Tom Hacohen <t...@stosb.com> wrote: > No, that is a no go, because you don't always want to methods as EAPI > (think internal classes). > > The correct thing would be to add the warning/error.
what are you talking about? It's the same that .eo.h does if you properly #define ..._PROTECTED... I'm not suggesting to change that behavior, just to auto-fix for the user when that is possible. -- Gustavo Sverzut Barbieri -------------------------------------- Mobile: +55 (16) 99354-9890 ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
