Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

BinGOs (7246)

BinGOs
  (email not shown publicly)
http://gumbynet.org.uk/

System administrator, part-time Perl hacker, full-time POE [perl.org] evangelist. One day he will be made to pay for his crimes.

He has some modules on CPAN [cpan.org]. They may or may not be useful

Journal of BinGOs (7246)

Monday January 08, 2007
03:35 AM

POE-Component-CPAN-YACSmoke-0.08

[ #32096 ]

So, I went and released POE-Component-CPAN-YACSmoke-0.08 to CPAN.

The biggest improvement has been the mungling of MSWin32 support so that we can now properly fork another perl instance.

This has been a long running issue with POE::Wheel::Run, in that one can't launch another instance of perl.

I have mungled it to work in PoCo-CPAN-YACSmoke by using Win32::Process to launch a new instance of perl.

And it seems to work. Hooray.

( I have started work on porting this technique back into POE::Wheel::Run, but it is not quite ready yet. Watch this space ).

There is a strange caveat though. I found when using the minismoker.pl that on MSWin32 it disliked getting the list of recent modules. I fixed this by manually creating a file containing a list of recent modules and used the command-line option --jobs, and it starting processing them. Weird, no. *shrug*

So maybe if some MSWin32 smoke testing people would like to have a go with it, I'd be grateful of any feedback.

>:o)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.