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. -- Tom. On Tue, Aug 16, 2016 at 6:49 PM, Gustavo Sverzut Barbieri < barbi...@gmail.com> wrote: > On Tue, Aug 16, 2016 at 11:43 AM, Felipe Magno de Almeida > <felipe.m.alme...@gmail.com> wrote: > > On Tue, Aug 16, 2016 at 11:39 AM, Tom Hacohen <t...@osg.samsung.com> > wrote: > >> On 16/08/16 15:38, Tom Hacohen wrote: > > > > [snip] > > > >>> According to Daniel there are no ifdefs in the .eo.c... So I don't > >>> understand the problem... > >> > >> Actually, I can see why there would still be a problem because of the > >> weak symbols thing. > >> > >> I guess the best way then, as you suggested is to do the ifndef. We can > >> probably do an error, not a warning. > > > > I've fell in this problem before, but don't remember which error I > received. > > It took me a while to figure out that I forgot to #define _PROTECTED. > > So the error would be good indeed. But only if there are some functions > > defined as protected. > > > > OTOH, can't the .eo.c file just re-declare the functions as weak symbols > > or something? > > this is what I propose... it's a matter of writing the EAPI method(); > > > -- > 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 > ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
