[E-devel] [YAPT] Chaining promises

Hi, Here's a question about promise chaining. C being what it is, it's harder to define a series like p.then().then() than it is in JS. And I can't find any good example in EFL code. Let's consider an abstract chain that I'll define as "download, unzip, show". (eg. download a zip file, unzip it

[E-devel] memory allocation perf

so for a while now i've been mumbling about possibly pulling in a custom memory allocator (generic one intended to replace malloc/calloc/realloc/free) because of various reasons. 1. move memory allocated for efl away from "apps" so the chances of walking over your memory segment into an efl one

Re: [E-devel] [YAPT] Promise instant resolution

On Thu, 29 Sep 2016 09:50:19 -0700 Cedric BAIL said: > Hi, > > On Thu, Sep 29, 2016 at 8:38 AM, Davide Andreoli > wrote: > > I'm starting this new thread to further discuss promises, thus the tag > > [YetAnotherPromiseThread] :) > > :-) > > > It

Re: [E-devel] [YAPT] Promise instant resolution

On Thu, 29 Sep 2016 17:38:17 +0200 Davide Andreoli said: > I'm starting this new thread to further discuss promises, thus the tag > [YetAnotherPromiseThread] :) > > It seems to me we are putting too much ideas/discussion in the other > threads in a so sparse way that is

Re: [E-devel] [YAPT] Promise instant resolution

On Thu, 29 Sep 2016 17:30:11 +0100 Tom Hacohen said: > On 29/09/16 17:03, Gustavo Sverzut Barbieri wrote: > > Next mainloop iteration is essential to make user code "always work", no > > special cases. > > > > This was in my other thread commentary about "resolved promise",

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: add e_util_open(), unify all callers of enlightenment_open

On Thu, 29 Sep 2016 17:13:38 +0200 Davide Andreoli said: > 2016-09-28 0:50 GMT+02:00 Carsten Haitzler : > > > On Tue, 27 Sep 2016 22:06:29 +0200 Davide Andreoli > > > > said: > > > > > 2016-09-27 17:19 GMT+02:00 Mike

Re: [E-devel] [YAPT] Promise instant resolution

On Thu, 29 Sep 2016 12:57:24 -0300 Felipe Magno de Almeida said: > On Thu, Sep 29, 2016 at 12:38 PM, Davide Andreoli > wrote: > > I'm starting this new thread to further discuss promises, thus the tag > > [YetAnotherPromiseThread] :) > >

[EGIT] [core/efl] master 01/01: Evas_Device: Fix API name.

bdilly pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=50f5704cc6b95ed30b25c668e2fc1679a4131279 commit 50f5704cc6b95ed30b25c668e2fc1679a4131279 Author: Guilherme Iscaro Date: Thu Sep 29 17:51:14 2016 -0300 Evas_Device: Fix API

Re: [E-devel] [EGIT] [core/efl] master 03/11: Evas_Device: Add evas_device_full_add() API.

Indeed. I created a diff for this problem. https://phab.enlightenment.org/D4325 On Tue, Sep 27, 2016 at 2:22 PM, Davide Andreoli wrote: > I think the "correct" name for this new API should be: > evas_device_add_full() > > > 2016-09-27 3:17 GMT+02:00 Guilherme Iscaro

Re: [E-devel] [YAPT] Promise instant resolution

Hi, On Thu, Sep 29, 2016 at 8:38 AM, Davide Andreoli wrote: > I'm starting this new thread to further discuss promises, thus the tag > [YetAnotherPromiseThread] :) :-) > It seems to me we are putting too much ideas/discussion in the other > threads in a so sparse way

Re: [E-devel] [YAPT] Promise instant resolution

On 29/09/16 17:03, Gustavo Sverzut Barbieri wrote: > Next mainloop iteration is essential to make user code "always work", no > special cases. > > This was in my other thread commentary about "resolved promise", that is, > to return a promise with a well known (resolved) value I completely agree,

[EGIT] [core/efl] master 01/01: efl: Update Efl.Model to use new Efl_Promise and Efl_Future

felipealmeida pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=1a2014a12234593f4ba27f2f76f87dc481447e7c commit 1a2014a12234593f4ba27f2f76f87dc481447e7c Author: Felipe Magno de Almeida Date: Thu Sep 29 13:12:09 2016 -0300

Re: [E-devel] [YAPT] Promise instant resolution

Next mainloop iteration is essential to make user code "always work", no special cases. This was in my other thread commentary about "resolved promise", that is, to return a promise with a well known (resolved) value Em quinta-feira, 29 de setembro de 2016, Felipe Magno de Almeida <

Re: [E-devel] [YAPT] Promise instant resolution

On Thu, Sep 29, 2016 at 12:57 PM, Felipe Magno de Almeida wrote: > On Thu, Sep 29, 2016 at 12:38 PM, Davide Andreoli > wrote: >> I'm starting this new thread to further discuss promises, thus the tag >> [YetAnotherPromiseThread] :) > > [snip] >

Re: [E-devel] [YAPT] Promise instant resolution

On Thu, Sep 29, 2016 at 12:38 PM, Davide Andreoli wrote: > I'm starting this new thread to further discuss promises, thus the tag > [YetAnotherPromiseThread] :) [snip] > The topic here is: do we really want to allow instant resolution of > promises? > For "instant

[E-devel] [YAPT] Promise instant resolution

I'm starting this new thread to further discuss promises, thus the tag [YetAnotherPromiseThread] :) It seems to me we are putting too much ideas/discussion in the other threads in a so sparse way that is starting to be difficult to follow the discussions and to understand when we found some

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: add e_util_open(), unify all callers of enlightenment_open

2016-09-28 0:50 GMT+02:00 Carsten Haitzler : > On Tue, 27 Sep 2016 22:06:29 +0200 Davide Andreoli > > said: > > > 2016-09-27 17:19 GMT+02:00 Mike Blumenkrantz < > michael.blumenkra...@gmail.com > > >: > > > > > discomfitor pushed a commit to branch

[EGIT] [tools/eflete] master 01/01: Project manager: correct handle result of fcntl func.

rimmed pushed a commit to branch master. http://git.enlightenment.org/tools/eflete.git/commit/?id=8ef3851a0b82240d57aab5453b8ceee8eed9d55b commit 8ef3851a0b82240d57aab5453b8ceee8eed9d55b Author: Mykyta Biliavskyi Date: Thu Sep 29 16:57:51 2016 +0300 Project

[EGIT] [tools/eflete] master 01/01: menu: rename menu items into more correct representation

rimmed pushed a commit to branch master. http://git.enlightenment.org/tools/eflete.git/commit/?id=3facb64120967604025d8cf0991602759c968ec7 commit 3facb64120967604025d8cf0991602759c968ec7 Author: Vitalii Vorobiov Date: Thu Sep 29 14:36:12 2016 +0300 menu: rename

[EGIT] [core/efl] master 01/04: eo - silence coverit "leak" on eo init if eoid table tls alloc fails

raster pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=c43308efb4e02849333bd5c1780dc8a149dd14ee commit c43308efb4e02849333bd5c1780dc8a149dd14ee Author: Carsten Haitzler (Rasterman) Date: Thu Sep 29 09:50:02 2016 +0900 eo -

[EGIT] [core/efl] master 04/04: eo - goto-ify a chunk iof code moving debug printfs out of hot paths

raster pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=6a5ae00ffaa20b6c1ccdd7891039d76b51099ced commit 6a5ae00ffaa20b6c1ccdd7891039d76b51099ced Author: Carsten Haitzler (Rasterman) Date: Thu Sep 29 15:29:34 2016 +0900 eo -

[EGIT] [core/efl] master 02/04: eo - remove pointless if found by coverity

raster pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=edf6507b9fe505aa068a91a95df9404fb0a29689 commit edf6507b9fe505aa068a91a95df9404fb0a29689 Author: Carsten Haitzler (Rasterman) Date: Thu Sep 29 11:36:03 2016 +0900 eo -

[EGIT] [core/efl] master 03/04: eo - fix error case lock not unlocking with shared objects from coverity

raster pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=f387818a55e9871f3e93ab0f83515919c527d69b commit f387818a55e9871f3e93ab0f83515919c527d69b Author: Carsten Haitzler (Rasterman) Date: Thu Sep 29 14:14:43 2016 +0900 eo - fix

[EGIT] [tools/eflete] master 01/01: Project manager: avoid situation with dereference pointer after free.

rimmed pushed a commit to branch master. http://git.enlightenment.org/tools/eflete.git/commit/?id=6a1a15e64dcaf4fa4a3c74a9a8fe64635a5abf21 commit 6a1a15e64dcaf4fa4a3c74a9a8fe64635a5abf21 Author: Mykyta Biliavskyi Date: Wed Sep 28 17:32:56 2016 +0300 Project