From: Nathan I. <nin...@gm...> - 2008-01-08 03:26:26
|
That would be reasonable as well, as long as it clearly indicates that it prevents or allows the callback from recurring. On Jan 7, 2008 6:12 PM, Michael Jennings <e-...@ka...> wrote: > On Tuesday, 08 January 2008, at 00:59:22 (+0100), > Peter Wehrfritz wrote: > > > > I want to add two aliases (ECORE_CALLBACK_KEEP and > > > ECORE_CALLBACK_REMOVE) to Ecore.h. They can be used as return > > > values for the ecore callbacks like timer, idler etc. Imho that > > > improves code-readability and helps (at least me) to write code, > > > because you don't have to remember if 0 stops the timer or keeps > > > it. > > > > I've talked with Nathan about it and he prefers > > ECORE_CALLBACK_STOP/REPEAT. > > _RENEW and _CANCEL would be more intuitive, IMHO. Just a thought. > > Michael > > -- > Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <me...@ka...> > Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) > ----------------------------------------------------------------------- > "It is strange to be known so universally and yet be so lonely." > -- Albert Einstein > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > |