On Thu, 15 Dec 2005 16:24:50 -0600 Brian Mattern <[EMAIL PROTECTED]> wrote:
> I haven't looked at ecore_exe / fd handlers / etc. However, in most > ecore handlers the return values are > > 0 - this handler is done, don't call it again / delete it > !0 - this handler is not done, call it again next time the event > comes up > > From your email, it sounds like that is how things work. However, you > are a little unclear about whether you are talking about return > values from the handler or return values from the buf_func, so I may > be misreading. This is how things work in fd handlers, unless there is a buf_func defined. Maybe the way to go is the other way, remove the special meaning when buf_func is defined. As mentioned, buf_func is only used once, and that may just be a performance hack that could be done some other way. > Also, in your last paragraph, you suggest documenting that a 0 return > means "keep calling me", when earlier you state that it is a > *non-zero* return that means "keep calling me"... Having 0 do this > would be contrary to the rest of ecore. Doh! Typo on my part.
pgpKXZ069G8DI.pgp
Description: PGP signature
