Re: unexpected _child(lose) for a detached session from _start

2009/11/20 Rocco Caputo <[email protected]>

> Agreed, a _child(lose) before the _child(create) is bad.
>

This a case of _child(lose) without any _child(create) ever (neither before
or after).


> It should either be a _child(create)/_child(lose) pair, or nothing in this
> case.

 I'm tempted to go with "nothing" since it would be hard to fix the
> create/lose timing.


I'm tempted to go with "nothing", as the session is declared detached.


> Also the new(detached => 1) seems good, but I admit I haven't given it much
> though yet.  Sometimes I change my mind after thinking about things too
> hard.
>
> If you haven't already, please submit this to [email protected].  I'm
> liable to forget about POE bugs, patches, tests, etc. if they're not in
> POE's bug tracker.
>

See bug #51772.


> Thank you again for all your help.


POE is helping me much, so thanks to you. It helped me to build my
application during the last 9 months. However, debugging is painful and I'm
still tracking a particular bug in my code for 3 weeks now. I just
discovered POE::API::Peek and it looks like it is the toolbox I was looking
for for months.

Olivier.