On Fri, 2004-12-03 at 12:21 +0000, Zefram wrote: > >Even though the Event API is inconsistent and quirky, I would like to > >strive for consistency where possible. > > You seem to be hinting that the ->active_watchers() interface is in > some way inconsistent with this watcher-number independence.
No. The embarrassing inconsistency is that the other watcher types do not offer this API. Signal watchers could easily offer this API. However, it doesn't make much sense for io, timers, or idle watchers. Hence, I hesitate to add this API especially since you don't need it. > By the way, the information available from ->active_watchers() can > already be obtained from other parts of the Event interface. The output > of Event::all_watchers() could be filtered to obtain the same list, > though by requiring the examination of all watchers this technique would > be rather inefficient. Correct, which is another reason not to add ->active_watchers(). -- A new cognitive theory of emotion, http://openheartlogic.org
signature.asc
Description: This is a digitally signed message part
