On Wed, Jan 3, 2018 at 11:07 AM, Andrew Williams <a...@andywilliams.me> wrote: > Hi, > > I was concerned that, as this had been added in a legacy header, it may > need to remain..?
not a legacy header, rather a "eo-only" and "c-only" header... usually for things that shouldn't be exposed to bindings, at least on an automated way. eina_promise_new() is the one that uses that function, it's not auto-generated by bindings. The idea is that high-level languages (Python, C#, C++...) will expose this using their native promise, so it's transparent... this all needs manual work, so exposing this method in ".eo" to be parseable by eolian will not be useful. I recall that was the reason to not put it in ".eo", just in eo-only and c-only header. -- Gustavo Sverzut Barbieri -------------------------------------- Mobile: +55 (16) 99354-9890 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
