Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Jean-Philippe André
Hi, On 17 August 2016 at 04:55, Gustavo Sverzut Barbieri wrote: > On Tue, Aug 16, 2016 at 3:37 PM, Tom Hacohen wrote: > > No, that is a no go, because you don't always want to methods as EAPI > > (think internal classes). > All eo symbols are currently marked as EOAPI which means EAPI EAPI_WEA

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Gustavo Sverzut Barbieri
On Tue, Aug 16, 2016 at 3:37 PM, Tom Hacohen 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 ..._PR

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Tom Hacohen
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

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Gustavo Sverzut Barbieri
On Tue, Aug 16, 2016 at 11:43 AM, Felipe Magno de Almeida wrote: > On Tue, Aug 16, 2016 at 11:39 AM, Tom Hacohen 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

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Tom Hacohen
On 16/08/16 15:38, Tom Hacohen wrote: > On 16/08/16 15:27, Tom Hacohen wrote: >> On 16/08/16 15:19, Gustavo Sverzut Barbieri wrote: >>> On Tue, Aug 16, 2016 at 11:09 AM, Tom Hacohen >>> wrote: On 16/08/16 14:48, Gustavo Sverzut Barbieri wrote: > On Tue, Aug 16, 2016 at 7:08 AM, Tom Hacohe

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Felipe Magno de Almeida
On Tue, Aug 16, 2016 at 11:39 AM, Tom Hacohen 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. >

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Tom Hacohen
On 16/08/16 15:27, Tom Hacohen wrote: > On 16/08/16 15:19, Gustavo Sverzut Barbieri wrote: >> On Tue, Aug 16, 2016 at 11:09 AM, Tom Hacohen wrote: >>> On 16/08/16 14:48, Gustavo Sverzut Barbieri wrote: On Tue, Aug 16, 2016 at 7:08 AM, Tom Hacohen wrote: > On 16/08/16 04:38, Gustavo Sverz

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Tom Hacohen
On 16/08/16 15:19, Gustavo Sverzut Barbieri wrote: > On Tue, Aug 16, 2016 at 11:09 AM, Tom Hacohen wrote: >> On 16/08/16 14:48, Gustavo Sverzut Barbieri wrote: >>> On Tue, Aug 16, 2016 at 7:08 AM, Tom Hacohen wrote: On 16/08/16 04:38, Gustavo Sverzut Barbieri wrote: > it seems at the end

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Gustavo Sverzut Barbieri
On Tue, Aug 16, 2016 at 11:09 AM, Tom Hacohen wrote: > On 16/08/16 14:48, Gustavo Sverzut Barbieri wrote: >> On Tue, Aug 16, 2016 at 7:08 AM, Tom Hacohen wrote: >>> On 16/08/16 04:38, Gustavo Sverzut Barbieri wrote: it seems at the end was a missing "#define ..._PROTECTED" in the .c fil

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Tom Hacohen
On 16/08/16 14:48, Gustavo Sverzut Barbieri wrote: > On Tue, Aug 16, 2016 at 7:08 AM, Tom Hacohen wrote: >> On 16/08/16 04:38, Gustavo Sverzut Barbieri wrote: >>> it seems at the end was a missing "#define ..._PROTECTED" in the .c >>> file that includes the generated .eo.c. >>> >>> I wonder: shoul

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Gustavo Sverzut Barbieri
On Tue, Aug 16, 2016 at 7:08 AM, Tom Hacohen wrote: > On 16/08/16 04:38, Gustavo Sverzut Barbieri wrote: >> it seems at the end was a missing "#define ..._PROTECTED" in the .c >> file that includes the generated .eo.c. >> >> I wonder: shouldn't the generated .eo.c write: >> #ifndef ..._PROTECTED >

Re: [E-devel] problems with eo method overloading

2016-08-16 Thread Tom Hacohen
On 16/08/16 04:38, Gustavo Sverzut Barbieri wrote: > it seems at the end was a missing "#define ..._PROTECTED" in the .c > file that includes the generated .eo.c. > > I wonder: shouldn't the generated .eo.c write: > #ifndef ..._PROTECTED > #define ..._PROTECTED > #endif > No. The .eo.c should be i

Re: [E-devel] problems with eo method overloading

2016-08-15 Thread Gustavo Sverzut Barbieri
it seems at the end was a missing "#define ..._PROTECTED" in the .c file that includes the generated .eo.c. I wonder: shouldn't the generated .eo.c write: #ifndef ..._PROTECTED #define ..._PROTECTED #endif On Mon, Aug 15, 2016 at 7:03 PM, Gustavo Sverzut Barbieri wrote: > Hi all, > > If you get

[E-devel] problems with eo method overloading

2016-08-15 Thread Gustavo Sverzut Barbieri
Hi all, If you get my branch devs/barbieri/efl-io-interfaces [1] you can see that the example efl_io_copier_example will fail to run with a strange error as below. The class hierarchy is: - Efl.Io.Reader (interface), defines "can_read" property. - Efl.Io.Reader.Fd (mixin on top of Efl.Io.Reade