On 12/14/07, Leandro Lucarella <[EMAIL PROTECTED]> wrote: [...] > I don't completely understand what's your plan, but I was planning to make > a C++ libev (native API) wrapper in the style of eventxx in the, hopefuly, > short term. Is that what you plan to do?
Leandro, can you please announce it if you do this? My desire is to have 2 wrappers, one over the "classic" libevent API (using eventxx) and one that only requires libev API, but can be interchanged very easily. This could make it easier for certain applications to migrate and take advantage of the improvements in the libev API. If you look in the project, there is a "ioevent" API that extends eventxx and also io++.h which tries to emulate a similar API over ev++.h. Perhaps some of my work should be taken as suggestions for possible enhancements to the original (eventxx and ev++) authors. On 12/14/07, Marc Lehmann <[EMAIL PROTECTED]> wrote: [...] > in any case, we all follow slightly different agendas - mine was to arrive > at a suitable perl interface and also replace my older "io_manager" > module which worked fine but extremely inefficient. ev++.h was designed > to replace io_manager in spriit for use it my projects (the actual syntax > became quite different in the end, but it still fully reflects the > io_manager interface style). ... and is much easier to embed than the original libevent-I find this useful for adding to the CINT C++ interpreter, for example. > eventxx on the other hand provides more generic callback functions, and > certainly more overall functionality (such as the dispatcher). i would > hope that at one point eventxx fills the "overall full powered interface" > niche while ev++.h stays a very primitive event-struct-only wrapper with > less but more streamlined functionality. Yes, I certainly found the eventxx a very good starting point-easy to learn! I would still like to take as much advantage as possible of the streamlined & embedding functionality of ev++.h, that is why I actually have 2 different "headers" in my project. > "whole seconds" (as used in ioevent.h) sounds a bit limiting, even if it > works for you. Agreed! Ultimately, I would like to make some kind of "rational number" timer, but this is not a top priority for me. > Of course I would like more widespread acceptance in millions of projects, > but as libev+EV actually fulfills all my personal needs in *my* projects. > > Maybe what you need to do is write your own event library at one point. It > took me almost a decade to realise this, and I only realiased it once I > actually wrote the second one :) Yes, possibly. Widespread acceptance is always best, but of course it must fulfill your needs. I had been thinking about a simpler "event loop" API... _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
