Re: [E-devel] Ecore bug due EO integration

2012-11-03 Thread Tom Hacohen
On 02/11/12 02:33, Carsten Haitzler (The Rasterman) wrote: > On Thu, 1 Nov 2012 18:53:32 -0200 Gustavo Sverzut Barbieri > said: > >> Hi all, >> >> As I always complain, the problems with those "easy" solutions such as EO >> macro and types hell is when you have incorrect usage. While the correct

Re: [E-devel] Ecore bug due EO integration

2012-11-01 Thread The Rasterman
On Fri, 2 Nov 2012 01:55:42 -0200 Gustavo Sverzut Barbieri said: > On Thu, Nov 1, 2012 at 10:33 PM, Carsten Haitzler wrote: > > > On Thu, 1 Nov 2012 18:53:32 -0200 Gustavo Sverzut Barbieri > > said: > > > > > Hi all, > > > > > > As I always complain, the problems with those "easy" solutions suc

Re: [E-devel] Ecore bug due EO integration

2012-11-01 Thread Gustavo Sverzut Barbieri
On Thu, Nov 1, 2012 at 10:33 PM, Carsten Haitzler wrote: > On Thu, 1 Nov 2012 18:53:32 -0200 Gustavo Sverzut Barbieri > said: > > > Hi all, > > > > As I always complain, the problems with those "easy" solutions such as EO > > macro and types hell is when you have incorrect usage. While the correc

Re: [E-devel] Ecore bug due EO integration

2012-11-01 Thread Cedric BAIL
On Fri, Nov 2, 2012 at 9:33 AM, Carsten Haitzler wrote: > On Thu, 1 Nov 2012 18:53:32 -0200 Gustavo Sverzut Barbieri > said: >> As I always complain, the problems with those "easy" solutions such as EO >> macro and types hell is when you have incorrect usage. While the correct >> path is all nice

Re: [E-devel] Ecore bug due EO integration

2012-11-01 Thread The Rasterman
On Thu, 1 Nov 2012 18:53:32 -0200 Gustavo Sverzut Barbieri said: > Hi all, > > As I always complain, the problems with those "easy" solutions such as EO > macro and types hell is when you have incorrect usage. While the correct > path is all nice and simple, the incorrect is tricky to solve. >

Re: [E-devel] Ecore bug due EO integration

2012-11-01 Thread Cedric BAIL
On Fri, Nov 2, 2012 at 5:53 AM, Gustavo Sverzut Barbieri wrote: > As I always complain, the problems with those "easy" solutions such as EO > macro and types hell is when you have incorrect usage. While the correct > path is all nice and simple, the incorrect is tricky to solve. > > Consider the f