On Sun, Nov 11, 2007 at 08:04:10PM +0100, Chris Brody <[EMAIL PROTECTED]> wrote:
> My first comment is that building with EV_MULTIPLICITY=1 (the default
> value) caused a few problems since there is both a struct ev_loop and
Thanks a lot (I really never tested with EV_MULTIPLICITY, so I am
pleasently surprised you even got some results... :)
> an ev_loop() function call. In addition, the EV_P (and EV_P_) macros
> require the user code to use "using namespace ev"...
user code should not need to use those macros... when does the need come
up?
(in fact, there should not be any macros defined, but I guess thats not
reasonable, so maybe in the long run ev will have to end up in the std
namespace)
> does exhibit a few quirks. For any C++ class that is called by
> interpreted code, CINT has to parse the header file and make a dynamic
> library that is called in reaction to interpreted C/C++ code. It is
> only "85%" compliant and has real trouble with significantly templated
> code.
Ok, I wonder wether ev++ counts as heavily templated or not :)
> But if I make a C++ subclass (or several C++ subclasses) that are less
> complex, these should be more straightforward to be used dynamically.
> I will try this and provide some more feedback.
Thanks!
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
