t; This is perl, v5.8.8 built for i486-linux-thread-multi
> Event-1.20
> IPC-Shareable-0.60
>
> Linux breslau 2.6.36 #2 SMP PREEMPT Thu Jan 13 10:56:43 EET 2011 i686 AMD
> Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD GNU/Linux
> Slackware 12.1.0
--
Joshua N. Pritikin
Department of Psychology
University of Virginia
Gilmer Hall 102; Charlottesville, VA 22903
http://people.virginia.edu/~jnp3bc
On Mon, Dec 29, 2008 at 01:41:53PM -0500, Jeff Boes wrote:
> Joshua N Pritikin wrote:
> > Let us know what happens!
>
> I am a bit confused, still. Should I make *all* my events reentrant,
The reentrant constraint is just for debugging. You don't want to keep
re-entering
On Mon, Dec 29, 2008 at 09:51:16AM -0500, Jeff Boes wrote:
> Hello! I posted this to the mailing list some time ago but never got a
> response.
I didn't see your post. Are you sure it got through?
> Do you have any insights?
>
> I'm upgrading an ancient (2004-era) server to the modern era:
>
>
On Thu, Dec 06, 2007 at 12:35:12PM +0200, Alexandr Ciornii wrote:
> Yes, I can build many other modules fine.
> You can see similar failures here:
> http://www.nntp.perl.org/group/perl.cpan.testers/2007/10/msg712278.html
> http://www.nntp.perl.org/group/perl.cpan.testers/2007/10/msg670107.html
Oh,
I don't do Windows so...
--
Make April 15 just another day, visit http://fairtax.org
--- Begin Message ---
Sorry the [EMAIL PROTECTED] address failed...
-- Forwarded message --
From: Simon Hardy-Francis <[EMAIL PROTECTED]>
Date: Oct 25, 2007 7:21 PM
Subject: event iocp request
To
On Fri, Jun 15, 2007 at 03:07:31PM -0300, Roberto Etcheverry wrote:
> I forgot to send you to minimum perl script that exhibits the problem.
> #!/usr/bin/perl
> use strict;
> use warnings;
>
> use threads;
> use Event;
>
> sub create_thread {
> warn "in create_thread() before async()\n";
>
This release just fixes a test which started breaking on a recent perl.
--
Make April 15 just another day, visit http://fairtax.org
On Sat, May 19, 2007 at 11:11:25AM +0100, Zefram wrote:
> Joshua N Pritikin wrote:
> >I don't think this message reached the mailing list?
>
> It did. I received it the first time, and I replied:
Hrm, somehow I missed your reply as well!
> $$ $] $^V
>
> Not many
I don't think this message reached the mailing list?
Can somebody suggest some other read-only variable or should I just
disable the test?
--
Make April 15 just another day, visit http://fairtax.org
--- Begin Message ---
eval { Event->var(@p, var => \$1) };
ok $@, '/read\-only/';
This
Can somebody suggest some other read-only variable or should I just
disable the test?
--
Make April 15 just another day, visit http://fairtax.org
--- Begin Message ---
eval { Event->var(@p, var => \$1) };
ok $@, '/read\-only/';
This seems to indicate that something that used to be read
Can anybody comment?
--- Begin Message ---
Hello,
I am just writing this e-mail because I think there is a bug in Event::generic,
I installed the Event pack using ppm and it installed everything just fine, but
whenever I try to use Event::generic I get an error in my cmd window, the error
is thi
The only change in this release is the application of the
patch by [EMAIL PROTECTED] to avoid some warnings in casts.
--
Make April 15 just another day, visit http://fairtax.org
--- Begin Message ---
The uploaded file
Event-1.08.tar.gz
has entered CPAN as
file: $CPAN/authors/id/J/JP/JP
I'd love to get a test suite addition for this change.
--- Begin Message ---
The uploaded file
Event-1.07.tar.gz
has entered CPAN as
file: $CPAN/authors/id/J/JP/JPRIT/Event-1.07.tar.gz
size: 251689 bytes
md5: 34b6eaf0b3658cd800b7d8727be7e9c4
No action is required on your part
Request
On Tue, Oct 10, 2006 at 01:25:51AM +0200, Marc Lehmann wrote:
> Event stores (c/typemap.c) a private pointer in mg_obj. This causes perl to
> crash (or, worse, silent memory corruption) whenever perl tries to duplicate
> the magic (e.g. when creating a thread, or forking under windows), as perl
> c
On Fri, Sep 22, 2006 at 03:32:28PM +0100, Oliver Rees wrote:
> I have been looking at your Event module to see if it might solve a
> problem I am experiencing with signal handling using perl 5.8.0 on Red
> Hat AS 3.
>
> I have a module which forks a number of processes and captures the
> exit c
Does anybody have any suggestions beside threads?
- Forwarded message from Eric Lenio <[EMAIL PROTECTED]> -
From: Eric Lenio <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Event.pm usage
Hi Joshua,
I'm not new to Perl but I am to Event.pm. I read the tutorial that comes with
Event.
On Thu, Aug 25, 2005 at 02:58:04PM +0200, Simon Hardy-Francis wrote:
> I've been developing with your Perl Event module and came up again a
> pitfall which took me some time to solve... maybe you would like to
> consider adding some kind of 'warning' or 'hint' into the Event
> documentation?
>
> T
On Tue, Jul 26, 2005 at 04:08:24PM +0100, Stracchino, Peri wrote:
> t/attach_to.t-1 139 36 200.00% 1-3
> t/bored.t-1 139 5 10 200.00% 1-5
> t/callback.t -1 139 6 12 200.00% 1-6
> t/delete.t -1 139 12 200.00% 1
> t/eval.t -1 139
our module (1.06 as I see you have posted recently on CPAN) to
contain the resolution.
Thanks again for your work and quick response, the patch came in time for me to
use your module in my next project (event-driven RPC server). :-)
Sincerely,
Eric Rybski
--- Joshua N Pritikin <[EMAIL PROT
Does the attached patch make Event work on 64 bit platforms?
--
If you are an American then support http://fairtax.org
(Permanently replace 50,000+ pages of tax law with about 200 pages.)
# This is a patch for Event-1.05 to update it to Event
#
# To apply this patch:
# STEP 1: Chdir to the sour
On Mon, 2005-05-02 at 09:42 -0700, Eric Rybski wrote:
>I've had no problems installing Event on Solaris 8 or 9 with 32-bit
> compiled
> perl, but have not been able to install it on a 64-bit (sparcv9) perl using
> the
> same build of GCC (3.4.2). Compilation works without a problem, but fail
This release is 1.04 + the recent memory leak fix.
signature.asc
Description: This is a digitally signed message part
On Sun, 2005-04-24 at 10:25 +0300, Nikita Savin wrote:
> > Does the attached patch work for you?
> Yep :) Thank you.
>
> When you plan to add Epoll support in Event.pm ?
When somebody submits a patch. Uri also suggested that libevent would
be smart to support because libevent wraps all the diff
On Sat, 2005-04-23 at 10:48 +0300, Nikita Savin wrote:
> > Can you confirm?
>
> Yes, no memory leak with Epoll::one_event()
OK, this is strange. I am passing G_VOID into a Perl_call_* function
and it's returning *1* instead of zero, which seems to be contrary to
the perlcall man page. (near ev.
On Sat, 2005-04-23 at 09:35 +0530, Joshua N Pritikin wrote:
> On Sat, 2005-04-23 at 07:37 +0530, Joshua N Pritikin wrote:
> > Is this memory leak in Event.pm or bad driver /dev/hands ?
>
> It appears to be a memory leak.
Looks like a bug in Event::loop(). I do not see any le
On Sat, 2005-04-23 at 07:37 +0530, Joshua N Pritikin wrote:
> Is this memory leak in Event.pm or bad driver /dev/hands ?
It appears to be a memory leak.
I recompiled Event with EVENT_MEMORY_DEBUG. However, that didn't turn
up anything. Hence, it's probably a mistake in refer
--- Begin Message ---
Hi!
Is this memory leak in Event.pm or bad driver /dev/hands ? :)
use Event;
Event->signal(signal=>'HUP', cb=>sub {kill 1, $$});
kill 1, $$;
Event::loop;
produce memory leak
--
Sincerely yours,
Nikita Savin
===
On Thu, 2005-03-31 at 20:11 -0500, Jeff Boes wrote:
> What I determined through experimentation is that you can set up a
> one-shot timer event, and then by doing --
>
> $e->stop;
> $e->at(time + $next);
> $e->start;
Hrm, looks like a bug?
> I dunno why the "stop" call is necessary, but the eve
The only change in this release is preliminary /dev/poll support. It is
"preliminary" because there is no config test to activate it. Sorry, I
just don't have enough time for this stuff. Patches welcome.
signature.asc
Description: This is a digitally signed message part
On Thu, 2005-03-24 at 12:20 +0100, [EMAIL PROTECTED] wrote:
> I extended unix.c to one additional mechanism (/dev/poll).
> According to available benchmarks this mechanism has
> much better performance as select or poll. I tested it only
> on Solaris. Do you think it would be a good idea to add
> t
On Sun, 2005-03-13 at 14:27 +0100, JÃrn Reder wrote:
> Joshua N Pritikin wrote:
> > Yah.
> >
> > I like the Event::RPC API. That's my cursory evaluation.
>
> So "contaminating" the Event namespace with it is Ok for you? ;)
Sure, but as Uri suggested,
On Sun, 2005-03-13 at 13:59 +0100, JÃrn Reder wrote:
> Uri Guttman wrote:
> > have you looked at Stem which is also based on event.pm? it does more
> > than RPC as it is message passing based and can do RPC, peer to peer and
> > multicast as well. find it on cpan or at stemsystems.com.
>
> I didn'
Hrm, sounds interesting.
So what does Event::RPC do exactly? Can you post a summary?
--- Begin Message ---
Hi Joshua,
I'm using your great Event module for a couple of years in several
client/server applications. Thereby a transparent object oriented RPC
mechanism emerged, based on Event.
I
On Tue, 2005-03-01 at 17:19 +1000, Maxim Nechaev wrote:
> The idea of "Event" module are great and i want use it my project. But
> i need watcher, that support SysV message queues. Unfortunately this
> watcher placed in demo directory and looks not complete.
> May i ask you, do you have any plans t
On Tue, 2005-02-01 at 13:17 +0100, Dariush Pietrzak wrote:
> Is my memory failing me, have Event ever had this property of time-outing
> long running callbacks?
Not by default.
> I found max_cb_tm in docs, but it doesent work:
> Event->timer(interval=>5,max_cb_tm=>1,cb=>sub {sleep 99;},);
The only difference between this release and 1.02 is a patch to allow
Event to compile on Win32.
signature.asc
Description: This is a digitally signed message part
Let's hope the addition of generic watchers doesn't break anything.
--
A new cognitive theory of emotion, http://openheartlogic.org
signature.asc
Description: This is a digitally signed message part
On Sun, 2004-12-05 at 23:06 +, Zefram wrote:
> Joshua N Pritikin wrote:
> >Correct, which is another reason not to add ->active_watchers().
>
> Strange: I see it as a reason in favour of the API.
Better to keep the API smaller and simpler in this case. If someone
requests
On Wed, 2004-12-01 at 01:23 +, Zefram wrote:
> +=head1 SYNOPSIS
> +
> + use Event::generic;
> +
> + $source = Event::generic::Source->new;
> +
> + $w = Event->generic(source => $source, ...);
> + $w = $source->watch(...);
> +
> + $source = $w->source;
> + $w->source($source);
> +
> + @watchers
On Fri, 2004-12-03 at 12:21 +, Zefram wrote:
> >Even though the Event API is inconsistent and quirky, I would like to
> >strive for consistency where possible.
>
> You seem to be hinting that the ->active_watchers() interface is in
> some way inconsistent with this watcher-number independence.
On Wed, 2004-12-01 at 01:23 +, Zefram wrote:
> +=item $source->active_watchers
> +
> +Returns a list of all the watchers that are currently actively watching
> +this event source. This is the set of watchers that will generate target
> +events when the C method is called on this source.
This
On Mon, 2004-11-29 at 22:56 +, Zefram wrote:
> >A useful way to view this is that occurrence of the source
> >event is not actually the arrival of the signal but triggers a
> >counting of the signal. Source events generate target events on
> >a schedule that depends on the operation of the even
This release is for Zefram.
--
A new cognitive theory of emotion, http://openheartlogic.org
signature.asc
Description: This is a digitally signed message part
On Mon, 2004-11-29 at 09:51 +, Zefram wrote:
> #!/usr/bin/perl
> use warnings;
> use strict;
> use Event;
> my $w;
> $w = Event->signal(signal => "USR1", cb => sub {
> print "handler got hits=", $_[0]->hits, "\n";
> kill "USR1" => 0;
> $w->stop;
> $w->start;
> });
> kill
On Sun, 2004-11-28 at 16:45 +, Zefram wrote:
> @@ -166,10 +217,16 @@
>
> Activate the watcher. Watchers refuse to C without
> sufficient configuration information to generate events. Constructors
> -always invoke C unless the C1> option is requested.
> +always invoke C unless the C<< park
Thanks Zefram, these are generally great patches. I'll merge them as
soon as I have a spare tuit.
--
A new cognitive theory of emotion, http://openheartlogic.org
signature.asc
Description: This is a digitally signed message part
Uh oh.
- Forwarded message from Yuval Kogman <[EMAIL PROTECTED]> -
From: Yuval Kogman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: weird behavior with Event
X-OpenPGP-Key: http://nothingmuch.woobling.org/gpg-key-0xEBD27418.asc
X-OpenPGP-Key-Fingerprint: C56E 126B C277 6DB7 237C 4A7C
Can anyone offer a clue?
- Forwarded message from [EMAIL PROTECTED] -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: question on IPC::LDT implementation with Event.pm
Hi Joshua,
Would like a little help from you. In your Event tutorial, you mention on
using non-blocking soc
On Mon, May 24, 2004 at 07:13:12PM +, Ton Hospel wrote:
> The docs don't seem to mention what happens to an Event loop() if there
> are no event sources anymore. I hoped it would unloop automagically,
Yah, it should.
> and it at least *seemed* to until I tried:
>
> #!/usr/bin/perl -wl
> use
- Forwarded message from Jeremy Howard <[EMAIL PROTECTED]> -
Subject: Event.pm 1.0 - nice work!
To: [EMAIL PROTECTED]
From: Jeremy Howard <[EMAIL PROTECTED]>
X-Sasl-Enc: BA6e2Q86SSxQ0HXW5XhmCA 1084941820
Hi Joshua,
Congrats on the Event.pm 1.0 release! Pretty cool module...
We have a lo
- Forwarded message from PAUSE <[EMAIL PROTECTED]> -
The uploaded file
Event-1.00.tar.gz
has entered CPAN as
file: $CPAN/authors/id/J/JP/JPRIT/Event-1.00.tar.gz
size: 245384 bytes
md5: be0eb302d8fb5729c500b32008023451
signature.asc
Description: Digital signature
On Thu, May 13, 2004 at 06:08:01PM +0200, Marc A. Lehmann wrote:
> Hi, with the current release of Event my programs start to fail with
> this error message:
>
>Event: attempt to invoke now() method with callback unset on watcher
>'??' at Event/t/00_basic.t line 13
Wow, I must have been
On Thu, Apr 29, 2004 at 05:16:22PM +0100, Zefram wrote:
> What really needs to be done with the Event API is not necessarily to
> get the cleanest handling of async events but to make it possible to
> handle them somehow. The API just doesn't permit these events to be
> handled properly. If you a
On Mon, Apr 26, 2004 at 10:58:06PM +0100, Zefram wrote:
> Joshua N Pritikin wrote:
> >Yah, OK, but is there a real-world justification for running
> >asynccheck when creating signal watchers? Or is this just a
> >theoretical cleanliness argument?
>
> I haven't tho
On Mon, Apr 26, 2004 at 10:32:26PM +0100, Zefram wrote:
> Joshua N Pritikin wrote:
> >Because merely calling asynccheck never eliminates the race condition.
> >It just makes it "shorter."
>
> It does eliminate the race condition, in that it makes ->pending retu
On Sun, Apr 25, 2004 at 04:13:50PM -0400, Jerry D. Hedden wrote:
> The implementation of the 'NO_TIME_HIRES' is flawed. The problem is
> that the code for the module is executed (i.e., if (!$NO_TIME_HIRES)
> {...}) before the import() function is called. Would it work to move
> the if block insid
On Thu, Apr 22, 2004 at 08:36:07AM +0100, Zefram wrote:
> And a final thought before I head off on holiday: consider the event
> sequence
>
> 0. start a signal watcher
> 1. receive a signal
> 2. start a second watcher for the same signal
> 3. send another signal
> 4. process events
>
> At the mom
On Thu, Apr 22, 2004 at 08:16:43AM +0100, Zefram wrote:
> Joshua N Pritikin wrote:
> >> 0. (bug) ->pending() should do an asynccheck
> >
> >That changes the documented behavior too much.
>
> How so?
Because merely calling asynccheck never eliminates the race con
On Wed, Apr 21, 2004 at 07:15:33PM +0100, Zefram wrote:
> Back to my SIGTSTP handler. Its basic operation is thus:
>
> 0. start
> 1. block SIGTSTP
> 2. stop the watcher, returning SIGTSTP to default handling
> 3. send a SIGTSTP to self
> 4. unblock SIGTSTP, thus letting the pending SIGTSTP be del
I haven't done a release for a long time. I hope I didn't botch
anything.
* lib/Event.pm: Simplify hooking into Time::HiRes. Add a
NO_HIRES_TIME export_ok symbol to turn off the probing.
* Event.xs: Remove U2time. Remove install_time_api().
* lib/Event.pod: More
On Tue, Apr 20, 2004 at 04:14:26PM -0400, hx wrote:
> hi perl-loop. i'm attempting to use Event, ithreads, and shared
> variables together. perl is 5.8.3, Event is 0.87. in particular, i'd
> like to create a watcher that watches a shared variable. sample code:
>
> #!/usr/bin/perl
> use warnings
On Wed, Apr 21, 2004 at 08:07:47AM +0100, Zefram wrote:
> Joshua N Pritikin wrote:
> >Thanks for the report. I fixed this bug in my code.
>
> Which behaviour does "now" have in your code?
It throws an exception if the callback is not set.
> Another bug: it's po
On Tue, Apr 20, 2004 at 09:05:17PM +0100, Zefram wrote:
> I have a need for a type of watcher for which events are only generated
> manually. I want this for event types along the lines of "redraw
> required": it's generated as a result of internal program logic, but
> I want it to be subject to p
On Mon, Apr 19, 2004 at 09:18:08PM +0100, Zefram wrote:
> Before I started using Event, I had a couple of signal handlers that,
> as part of their work, locally modified the handling of their signal.
> The interesting case is with SIGTSTP: after doing some application
> cleanup, it would temporaril
On Tue, Apr 20, 2004 at 12:00:15AM +0100, Andy Mortimer wrote:
> Zefram writes:
> > After they've fired, they still exist and can be modified and retriggered.
> > See the "again" method. You need to explicitly cancel your watchers.
>
> Yep, that works, thanks muchly!
>
> I'm still slightly puzzl
On Mon, Apr 05, 2004 at 11:59:40AM -0400, Jerry D. Hedden wrote:
> Again, to keep this from affecting my application, I had to edit
> Event.pm to not use Time::HiRes. Is there another way to turn off
> using Time::HiRes in Event? If not, I'd like to request adding one.
Just call Event::install_t
On Fri, Apr 02, 2004 at 09:10:18PM -0500, Jerry D. Hedden wrote:
> I have determined that there is a definite bug in the Event module.
> I have a fairly involved newsgroup reading application that I
> recently converted to using the Event module. One of the timers is
> supposed to report the appl
On Wed, Feb 18, 2004 at 12:50:27AM +, Robin Redeker wrote:
> i am wondering why my program always unloops after a couple of time.
> When there are no events or just one poll for read on a listening
> socket, my program started to unloop after some time...around 5-10 minutes after
> invocation.
- Forwarded message from Kiss Gabor <[EMAIL PROTECTED]> -
From: Kiss Gabor <[EMAIL PROTECTED]>
Organization: CData Bt.
To: [EMAIL PROTECTED]
Subject: NetServer-Portal-1.08
Dear Joshua,
Are you developing NetServer-Portal yet?
May add a minor item to the wishlist?
NetServer::Portal::Top
- Forwarded message from David Muir Sharnoff <[EMAIL PROTECTED]> -
From: David Muir Sharnoff <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: a quick Event question.
When reentrant => 0 will a call to ->now():
1. run regardless
2. run now as long as the current callb
- Forwarded message from Tom Howe <[EMAIL PROTECTED]> -
From: Tom Howe <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Perl Event
Hi, I have a query regarding Event. I am trying to build a network server
that can take various requests from different clien
- Forwarded message from Robert Urban <[EMAIL PROTECTED]> -
To: [EMAIL PROTECTED]
Subject: Event and non-Event signal handlers on Linux
From: Robert Urban <[EMAIL PROTECTED]>
X-Seen: false
X-ID: [EMAIL PROTECTED]
Hallo Joshua,
hmm. I'm afraid I was a bit premature with my previous mail.
- Forwarded message from Robert Urban <[EMAIL PROTECTED]> -
To: [EMAIL PROTECTED]
Subject: AF_UNIX sockets and Event.pm
From: Robert Urban <[EMAIL PROTECTED]>
Hello,
I have written a simple script which uses Event->io on an UNIX socket.
The script functions as desired.
A (linix) "strac
- Forwarded message from Robert Urban <[EMAIL PROTECTED]> -
To: [EMAIL PROTECTED]
Subject: wish-list item for Event.pm
From: Robert Urban <[EMAIL PROTECTED]>
X-Seen: false
X-ID: [EMAIL PROTECTED]
Hello Joshua,
I just noticed that if I install a watcher for SIGCHLD, then perform
a waitpi
- Forwarded message from "Randal L. Schwartz" <[EMAIL PROTECTED]> -
To: Joshua Nathaniel Pritikin <[EMAIL PROTECTED]>
Subject: Event-0.87 failed on darwin
From: [EMAIL PROTECTED] (Randal L. Schwartz)
Is this a failure of Event, the test case, darwin, or 5.8? Should I
be worried?
t/
Thanks for the patch.
- Forwarded message from Perl Authors Upload Server <[EMAIL PROTECTED]> -
Subject: Notification from PAUSE
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED],
"Joshua Nathaniel Pritikin" <[EMAIL PROTECTED]>
From: "Perl Authors Upload Server" <[EMAIL PROTECTED]
- Forwarded message from Pascal Ronecker <[EMAIL PROTECTED]> -
Subject: Event module
From: Pascal Ronecker <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Organization:
Hi !
I'm trying to install the Event perl module,
perl Makefile and make works apparently fine, except that :
In file incl
- Forwarded message from mixo <[EMAIL PROTECTED]> -
From: mixo <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Event-0.86
Hi,
I am currently testing some perl software wich use your "Event" module.
The problem I have is that the program sef faults as soon as is call
"Event::loop()"
m
- Forwarded message from "Paul J. Kissman" <[EMAIL PROTECTED]> -
From: "Paul J. Kissman" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Event 0.86 fails make test
I am trying to install Event-0.86 on a Redhat system with Perl 5.8.0 and
have encountered the following problem:
During
- Forwarded message from Andreas Meier <[EMAIL PROTECTED]> -
From: Andreas Meier <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Event.pm 0.86 failed test t/var
X-Authenticated-Sender: #[EMAIL PROTECTED]
X-Authenticated-IP: [213.6.105.145]
X-Flags: 0001
Joshua,
I just tried to compile
On Mon, Oct 28, 2002 at 04:14:56PM -, Peter Galbavy wrote:
> Hope you have a minute to help. I am trying to use the Event module as the
> basis for a very simplistic scheduler to do multi-host pinging etc.
>
> I would like to schedule a heap of events and then set one callback as the
> underly
On Thu, Aug 29, 2002 at 04:03:18AM +0700, Luong Mai Em wrote:
> Dear Mr. Joshua N. Pritikin,
>
> I am a beginner of Perl development from Viet Nam. I try use your Event Package for
>my project on windows. But I don't known how to compile this package on windows
>plat
On Mon, Aug 19, 2002 at 11:57:09AM -0400, Jeff Boes wrote:
> I remain confused about a technique that I'm sure is available in Event,
> but I can't puzzle it out.
>
> Say I have two events, both 'timer' type. One event is a 'heartbeat'
> report to another process, saying "I'm still alive, and I
On Wed, Aug 21, 2002 at 03:43:58PM -0400, Jeff Boes wrote:
> Does an idle event have a default priority?
Try:
warn $watcher->prio;
warn $event->prio
> I have a pair of events. One's an idle event, with no 'prio' value in
> its constructor. Another is a timer event with a priority of '0'.
On Fri, Aug 02, 2002 at 10:20:37AM -0400, Jeff Boes wrote:
> Are there any tricks to getting Event to trigger when a socket receives
> input? I'm doing something equivalent to:
>
> $sock_in = IO::Socket::INET->new(
> LocalPort => $cfg->socket_nbr,
>
On Thu, Jun 27, 2002 at 12:37:27PM -0400, Jeff Boes wrote:
> What might these messages mean?
>
> Event: 'NEW_JOB_INDEX' was unexpectedly closed at
> /usr/local/lib/perl5/site_perl/5.6.1/i686-linux/Event.pm line 148
It means that the fd associated with the io event called 'NEW_JOB_INDEX'
was clos
On Tue, Jun 18, 2002 at 06:31:45PM +0200, Jochen Stenzel wrote:
> > What I'm wondering is whether Event->io does anything differently if you
> > supply min and max versus if they are omitted.
>
> all watcher types share several "base" attributes, but min and max are
> "extra" attributes that are
On Mon, May 27, 2002 at 02:33:01AM -0400, Allen Smith wrote:
> I'm holding my head over this one. A combination of Event-0.86 and
> BSD::Resource 1.15 coredumps with the following test.pl script:
>
> [..snip..]
>
> The change that I'm guessing is responsible (although I really don't know
> how) is
On Sat, May 25, 2002 at 07:06:53PM -0400, Allen Smith wrote:
> > Since the Event::io module is very flexible in regards to what events can
> > be "waited" for: Why not introduce another set of conditions, like
> > "urgent" ('u') or "out-of-band" ('o') to still provide the functionality
> > for tho
- Forwarded message from PAUSE <[EMAIL PROTECTED]> -
Reply-To: [EMAIL PROTECTED]
Subject: CPAN Upload: J/JP/JPRIT/Event-0.86.tar.gz
From: PAUSE <[EMAIL PROTECTED]>
To: "Joshua Nathaniel Pritikin" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
The uploaded file
Event-0.86.tar.gz
has
On Wed, May 22, 2002 at 09:02:36AM +0200, Clemens Schrimpe wrote:
> Having had a fresh start this morning I played a bit with your code and
> figured it:
>
> In the "HAS_POLL" version of pe_sys_multiplex() I replaced
>
> if (ev->poll & PE_W) bits |= (POLLOUT | POLLWRBAND);
> with
> i
On Tue, May 14, 2002 at 10:04:51AM +0100, Nick Ing-Simmons wrote:
> >In Event.xs, I change _loop() to:
> >
> >PROTOTYPE: ;$
> >CODE:
> >double maxtm = 60;
> >if (items == 1) maxtm = SvNV(ST(0));
>
> What frees the maxtm SV ?
Huh? maxtm is a double. ST(0) is on the stack. As fa
On Mon, May 13, 2002 at 06:32:04PM -0400, Bradley Brahms wrote:
> To do this, one would add the following to their script:
>
> Event->timer(interval => 5, cb => sub{unloop;});
>
> then change their Event::loop; line to
> while (1) {
> Event::loop;
> }
i think this is the sam
On Mon, May 13, 2002 at 12:51:54PM +0100, Nick Ing-Simmons wrote:
> Joshua N Pritikin <[EMAIL PROTECTED]> writes:
> >On Thu, May 09, 2002 at 05:42:38AM -0700, Scott Beck wrote:
> >> Sorry to bother you, the problem I was having was my own. The code was
> >> inco
On Sun, May 12, 2002 at 06:17:33PM -0400, Bradley Brahms wrote:
> I verified Allen's test under linux. I also tested one_event() which had an
> advantage that it will go to sleep if no events are available. one_event()
> also showed no growth.
This is all very strange. i'd accept a patch to re
On Sun, May 12, 2002 at 01:10:03AM -0400, Allen Smith wrote:
> On May 11, 11:28pm, Joshua N Pritikin wrote:
> > That means that Event probably has a reference counting bug.
>
> Sigh... yes. I am wondering myself about a couple things in ev.c:
> A. pe_event_invoke. Cal
On Sat, May 11, 2002 at 07:30:24PM -0400, Bradley Brahms wrote:
> as I have mentioned before I have tried the script with various
> combinations of perl/malloc on Solaris 7. I have now tried the same script
> on Linux with the following configurations:
> Linux 2.2.13-4 gcc 2.
On Fri, May 10, 2002 at 07:53:11PM +, [EMAIL PROTECTED] wrote:
> I have confirmed that even a Event->timer will grow the
> stack on and on and on.
i can reproduce the problem on my machine with perl 5.6.1.
If you look at the XS implementation of _loop(), you will see that
i call ENTER/SAVET
On Sat, Feb 09, 2002 at 09:22:57AM -0500, Colin Murtaugh wrote:
> I can try that. I know that if I just open a file and do a "while
> ()" loop to read it, it blocks when there's no input. That's fine
> as long as that file is the only source of events, but I want to have
> others as well.
Yah
On Fri, Feb 08, 2002 at 03:37:17PM -0500, Colin Murtaugh wrote:
> I'm trying to use Event.pm to do some pretty basic event handling
> (watching for incoming data on a named pipe, and eventually some timers)
> but I keep having trouble with CPU usage. Seems that once the loop
> starts, my script u
1 - 100 of 338 matches
Mail list logo
