Re: [E-devel] EFL Beta API

2013-07-30 Thread Gustavo Sverzut Barbieri
the infamous #ifndef EO_IS_UNDER_DEVELOPMENT_AND_API_WILL_CHANGE_AND_I_KNOW_ABOUT_THAT; #error "Eo is under development and API will change"; #endif should help. I don't mind the actual libname/release it we make sure the code is aware of that. On Tue, Jul 30, 2013 at 5:28 AM, Cedric BAIL wrote:

Re: [E-devel] EFL Beta API

2013-07-30 Thread Cedric BAIL
On Tue, Jul 30, 2013 at 8:56 AM, Lucas De Marchi wrote: > On Tue, Jul 23, 2013 at 5:29 AM, Cedric BAIL wrote: >> On Tue, Jul 23, 2013 at 5:04 PM, Michael Blumenkrantz >> wrote: >>> sure, but it sounds more like "pre-alpha" than beta at this point >>> considering the amount of rewrite occurring.

Re: [E-devel] EFL Beta API

2013-07-29 Thread Lucas De Marchi
On Tue, Jul 23, 2013 at 5:29 AM, Cedric BAIL wrote: > On Tue, Jul 23, 2013 at 5:04 PM, Michael Blumenkrantz > wrote: >> sure, but it sounds more like "pre-alpha" than beta at this point >> considering the amount of rewrite occurring. > > There is still no agreement about if we are going to change

Re: [E-devel] EFL Beta API

2013-07-23 Thread Tom Hacohen
On 23/07/13 08:46, Cedric BAIL wrote: > Hello, > > As the time comes, we are trying to move to a time based release. But > as the discussion on Eo does show, it takes time to reach a consensus > on some API and make it difficult to move forward on a release. > > So I have introduced a macro EFL_BET

Re: [E-devel] EFL Beta API

2013-07-23 Thread Cedric BAIL
On Tue, Jul 23, 2013 at 5:04 PM, Michael Blumenkrantz wrote: > sure, but it sounds more like "pre-alpha" than beta at this point > considering the amount of rewrite occurring. There is still no agreement about if we are going to change any of the existing API or not. It is still a discussion. And

Re: [E-devel] EFL Beta API

2013-07-23 Thread Michael Blumenkrantz
sure, but it sounds more like "pre-alpha" than beta at this point considering the amount of rewrite occurring. On Tue, Jul 23, 2013 at 9:01 AM, Cedric BAIL wrote: > On Tue, Jul 23, 2013 at 4:56 PM, Michael Blumenkrantz > wrote: > > I don't understand why we can't just remove all those from the

Re: [E-devel] EFL Beta API

2013-07-23 Thread Cedric BAIL
On Tue, Jul 23, 2013 at 4:56 PM, Michael Blumenkrantz wrote: > I don't understand why we can't just remove all those from the public > headers. If we're still rewriting them so much that they need to be marked > as beta, they should not be released at all imo. Because we use it. That's the point.

Re: [E-devel] EFL Beta API

2013-07-23 Thread Michael Blumenkrantz
I don't understand why we can't just remove all those from the public headers. If we're still rewriting them so much that they need to be marked as beta, they should not be released at all imo. On Tue, Jul 23, 2013 at 8:46 AM, Cedric BAIL wrote: > Hello, > > As the time comes, we are trying to m

[E-devel] EFL Beta API

2013-07-23 Thread Cedric BAIL
Hello, As the time comes, we are trying to move to a time based release. But as the discussion on Eo does show, it takes time to reach a consensus on some API and make it difficult to move forward on a release. So I have introduced a macro EFL_BETA_API_SUPPORT that is used to disable API that we