Hi again. There's progress being made in POE's signal handling.
If you've been reading along, you know that signals are dispatched differently now. Unlike normal deprecations, this one can't be staged over the course of three months. If your program relies on signals, please check out POE from CVS and give it a try. Yesterday some changes were committed regarding the handling of terminal signals. A new Kernel method, sig_handled(), has been added. It's vastly preferred over return values in signal event handlers. In fact, the significance of return values in signal handlers is now deprecated. The next commits will begin deprecating the _signal event. This has a large possibility of breaking existing code. Fortunately, it CAN be phased in over the next three CPAN releases. It will be recommended that sessions use sig() from now on to explicitly handle signals they're interested in. These changes (and more) have been on display in the planning department for some time. If you're just tuning in, have a look at http://poe.perl.org/?POE_RFCs/Signal_Reforms ... it will also be updated with change statuses as (or at least shortly after) things happen. If you're worried about the change schedule being too fast, see http://poe.perl.org/?POE_RFCs/Change_procedures ... This page outlines how staged and atomic changes are generally carried out. Thanks for reading. Feedback's very welcome. -- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sf.net
