RE: [NeoStats-Devel] Core CTCP event handling

M wrote:
> Justin Hammond wrote:
> 
> > If only it was that simple. For the actual Event calls, that works 
> > like a dream, but I hit problems with all the Event Modification 
> > functions (enable, flags etc). Without adding a extra flag to those 
> > functions, its difficult to tell if you want to modify the 
> C function 
> > or perl function, and you also hit problems if you have different 
> > flags for perl and C calls.
> > 
> > I'm sure your not going to like what I done to the event subsystem, 
> > but I couldn't think of another way around it. :)
> 
> You are correct I do not like what you have done. The 
> particular issue I have with it is it no longer compiles 
> without Perl and as you know I cannot compile on any platform 
> whatsoever with perl.

I have got it compiling and the event system working again on a non perl
compile. 

I have tidied up the code a lot to remove the strange while(1), flags and
multiple ifdef code paths so we again have a single code path with simple
legible checks for the perl path which should perform exactly as the
original. Obviously I cannot test the perl side.

Mark.