Hello
as usual i am stuck
making the following:
print(sending out batch \n);
my $task = POE::Wheel::Run-new
»···( Program = sub {·
»··· print(about to spawn batch\n);
»··· $actor-batch($job)·
»··· },
»··· StdoutFilter = POE::Filter::Reference-new(),
On Sat, Feb 14, 2004 at 06:53:44AM -0500, [EMAIL PROTECTED] wrote:
Taking Chris' question further... why not implement wait queues (I'm
thinking along the lines of NT). Any session could declare it's interest
on a waitable object... and anyone with a reference to that object could
call
On Sun, Feb 29, 2004 at 05:19:27PM +0100, Bruno Boettcher wrote:
print(sending out batch \n);
my $task = POE::Wheel::Run-new
»···( Program = sub {·
»··· print(about to spawn batch\n);
»··· $actor-batch($job)·
»··· },
»··· StdoutFilter =
On Wed, Feb 25, 2004 at 10:39:51PM -0800, Erick Calder wrote:
pulling it into the core with a name like POE::Arguments
side note: my vote would go for POE::Args. one thing I've always liked
about perl and detested about Java is the length of namespaces. I for one
hate to type so shorter
On Wed, Feb 18, 2004 at 08:13:15PM +, James Brown wrote:
Hi All,
A quick question here.
I have read the POE Cookbook example on broadcasting events (more
correctly, multicasting events) to various sessions and I'd like to
implement it (for keypress events) in my program.
I intend
The test reforms cannot wait for this thread to resurrect.
I intend to begin prototyping tests based on the ideas outlined at
http://poe.perl.org/?POE_RFCs/Test_Reforms. I'll post the code to
the list when it becomes a useful illustration of the process.
Discussion remains open on that plan and
