On Fri, Nov 09, 2007 at 01:19:02PM +0100, Chris Brody-GMail <[EMAIL PROTECTED]>
wrote:
> with the following flags to workaround a priority event issue:
> -Dev_flags=1 -DEVLIST_ACTIVE=1. This both solves a compile error and
(omg, this works????!?!?!?!) :)
Now, I always considered mucking with the flags as bad style (its internal
and should not be used by apps), but of course its in the header file and
not being documented means nothing.
Maybe this should be supported (which is not easy, however).
Or maybe one should fake it by simply adding a ev_flags field and dummy
#defines for EVLIST_ACTIVE.
> First I got the following errors:
> ./eventxx: In destructor `eventxx::dispatcher::~dispatcher()':
> ./eventxx:794: error: cannot convert `eventxx::internal::event_base*'
> to `event_base*' for argument `1' to `void
> eventxx::internal::event_base_free(event_base*)'
yeah, thats a known bug, but I wondered how many compilers would get it wrong
when writing that code.
> Very strange, but by declaring struct event_base at the beginning of
Thats indeed very weird. No, I have no problems whatsoever with that
change (its actually much cleaner that way, I think), thanks for tracking
it down, it'll be in CVS in a few hours.
--
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
