Re: Win32 AS Perl 5.8.8

They tried ...
http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/POE-0.34.txt
- still a fail on most of their build platforms.

Just in case it's useful, I've moved up to AS Perl 5.8.8 Build 817,
Komodo 3.5.3 beta 1, and installed POE 0.34 from the CPAN shell. (CPAN
hasn't previously worked for me from AS Perl, but the new preconfigured
CPAN has sensible paths set, so is painless to use now).

I skipped the network tests when given the option, and also noticed that
on Win32, the signal tests are all skipped. Is that the correct thing to
do, as there is some signal functionalilty in AS Perl? All the tests
that did run completed successfully.

I still have the SIGALARM generated in the Komodo debugger as soon as
POE code entered, but ignoring it explicitely in my app code seems
harmless. I'll bug AS about why I must do that.

Thanks for your Win32 efforts,
Steven

Rocco Caputo wrote:

> On Mar 30, 2006, at 13:33, D D Allen wrote:
>
>> I started with the Poe Tk cookbook example (
>> http://poe.perl.org/?POE_Cookbook/Tk_Interfaces) which runs fine.  My
>> first exploratory change was to change the line
>> "$_[KERNEL]->yield("ev_count");" in the ui_count sub to
>> "$_[KERNEL]->delay("ev_count", .5);" so that the counter is updated 
>> twice
>> per second as opposed to continuously (as fast as Poe can generate 
>> events)
>> -- which works as intended -- but has the side-effect that when I 
>> click close on the Tk window, while the window goes away, the Perl
>> script
>> doesn't terminate as expected.  It just sits there until I kill it  with
>> Ctrl-C.   The cookbook example doesn't include a _stop so I added 
>> one that
>> includes a print.  The _stop sub is called as expected and returns 
>> -- but
>> the script never appears to return from "$poe_kernel->run();".
>
>
> Fixed and committed.  Also released, but shhhhh!  That hasn't been 
> announced yet.
>
> I'm waiting for http://ppm.activestate.com/BuildStatus/5.8-windows/
> windows-5.8/POE-0.34.txt to appear so I can check out any issues with 
> the new installer.
>