--- a/qmsk/net/lib/event2/base.pxd	Sat Sep 26 22:09:24 2009 +0300
+++ b/qmsk/net/lib/event2/base.pxd	Sat Sep 26 23:38:02 2009 +0300
@@ -9,11 +9,9 @@
         An event_base stores the "global" state associated with events - it holds a set of events (pending/active/scheduled),
         and uses some specific multiplexing method (select/poll/epoll/kqueue/etc) to drive these events.
         
-        Constructs a new event_base with default parameters.
+        
+        *** POSIX Signal Handling ***
 
-        XXX: you must keep a reference to the event_base around yourself!
-        XXX: what happens to events once we are destructed?
-        
         Libevent has its own asynchronous signal-handling mechanism that is incompatible with Python's signal-handling
         mechanism.
         
@@ -31,14 +29,15 @@
         This means that python's default signals and any other signals added using the signal module continue to work
         at the cost of some additional complexity, but any libevent signal-events also work as well :)
         
-        XXX: currently, you can only have one event_base at a time - there should be separate types used for the main
+        *** TODO ***
+
+        Currently, you can only have one event_base at a time - there should be separate types used for the main
         thread and sub-threads, since the python signal handling mechanism only works in the main thread.
 
-        XXX: the propagate-exceptions doesn't actually work either, it just aborts the event loop :)
+        The propagate-exceptions doesn't actually work either, it just aborts the event loop :)
 
-        XXX: add support for event_config!
-        XXX: add support for event_base_priority_init!
-
+        Support for event_config!
+        Support for event_base_priority_init!
     """
     
     # the underlying ev_base object