On Fri, Aug 17, 2001 at 01:22:55PM +0200, Jochen Stenzel <[EMAIL PROTECTED]>
wrote:
> >Are the event objects being reused in a way that makes it impossible to
> >extend their life over the callback itself?
>
> Hm. What I'm asking myself thinking about this is what special kind of
> information is provided by stored (but already handled) Event::Event
i found the problem: event indeed does not like it when I try to use
event objects after the callback returns. (this is bad and forced me to
implement my own event object wrapper).
> objects in your queue (taking into account that this is an intermediate
> structure just built for the callback) ... is this an information that
> cannot be catched another way? Could it be stored for itself, without
> the Event::Event object?
sure.i can make a copy. but what sense does it make to copy a perl
structure when you just can store it in a variable ;)
anyway, this could be documented, but I worked around it, so no problem.
> cause trouble, but to answer this, I assume we have to wait for Joshua
> or have to look at the code ...
explains it well (I just want that fixed Event-0.84 ;)
thx ;)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
