On Fri, Dec 15, 2017 at 11:13 AM, Carsten Haitzler <[email protected]> wrote: > On Fri, 15 Dec 2017 07:07:53 +0100 Vincent Torri <[email protected]> > said: > >> On Fri, Dec 15, 2017 at 6:30 AM, Carsten Haitzler <[email protected]> >> wrote: >> > I've been working on this for a while and now have things in a pretty good >> > state. I just pushed a commit that does a huge amount of this (not all - >> > see >> > 5dd52fd09b7d79c70b3134423a87aa6400a2d994). But it's a huge step to efl loop >> > objects really being self contained. >> > >> > efl loop fd didn't handle windows so i put in efl loop handlers that handle >> > both fd's, file fd's and win32 handles. >> >> i would like to use on win32 handlers on Windows (so no select() API >> usage). Maybe that could simplify a bit ? > > ? i'm not sure what you mean/ the efl loop handler allows for fds, (socket, > file) AND for win32 handles. the handler can listen to any one of these 3.... > it's there.it's the api. the implementation is the same as before.
currently, on Windows, depending on the context, we should use either the win32 handlers or the fd ones if, on Windows, we call only the win32 handlers, maybe one can have one common API, which use wi32 handlers on Windows and fd ones on !Windows. No need to have #ifdef _WI32 etc... anymore i don't know if it is possible with what you are doing, but it is a thought Vincent ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
