On Fri, 13 Jan 2006 12:28:51 +0100 Sebastian Dransfeld
> enlightenment-cvs@... wrote:
> > Enlightenment CVS committal
> > Author : onefang
> > Project : e17
> > Module : libs/ecore
> > Dir : e17/libs/ecore/src/lib/ecore
> > Modified Files:
> > Ecore.h ecore_exe.c ecore_signal.c=20
> > Log Message:
> > Minor API breakage and fixage.
> BTW. ECORE_EVENT is correct since ecore_exe is in the main ecore dir
> and lib. If it should be ECORE_EXE, then ecore_exe should be a subdir=20
> below ecore/src/lib
This has been discussed here for a week. The change is for consistency
from the point of view of the coder using it. This coder doesn't care
how things are organised internally, they just care that other, similar
things are called ECORE_*_EVENT_*.
ecore_exe has grown a bit recently, and now has lots of similarities to
ecore_con and ecore_ipc due to the fork'n'pipe IPC. I'm trying to iron
out the differences to make life easier for coders using them. It's
all IPC, even if ecore_exe can be used without the IPC component, and it
should all work in similar ways, with similar names.
Get latest updates about Open Source Projects, Conferences and News.