on-topic-content:
The first larger program using coroutines is now doing "mission
critical" work (failure == loss of relatively unimportant data). It's
my news-scanner which scans ~60 servers at the same time. It's just as
fast (600k/s is where the network tops out), requires only slightly more
m
> "PCG" == <[EMAIL PROTECTED]> writes:
PCG> On Mon, Jul 16, 2001 at 04:46:36AM -0700, Joshua Pritikin
<[EMAIL PROTECTED]> wrote:
PCG> Boy, I just learned more about perl internals than I ever imaged. The
PCG> only thing remaining is the regex machine and the exact details of this
On Mon, Jul 16, 2001 at 04:46:36AM -0700, Joshua Pritikin <[EMAIL PROTECTED]>
wrote:
> >I hope you found this posting somewhat entertaining...
>
> Wow! Outstanding!
Boy, I just learned more about perl internals than I ever imaged. The
only thing remaining is the regex machine and the exact det
On Mon, Jul 16, 2001 at 04:46:36AM -0700, Joshua Pritikin <[EMAIL PROTECTED]>
wrote:
> >I hope you found this posting somewhat entertaining...
>
> Wow! Outstanding!
it does not work (as i just found out), however, as perl doesn't like the
same sub to be entered from two different coroutines at
<[EMAIL PROTECTED] ( Marc) (A.) (Lehmann )> wrote:
>it is difficult to get the point across using a small program - the idea
>is to linearize programs, while still using the benefits of a state
>machine.
>
> ...snip...
>
> but given that I thought this to be much too complicated for many
I recently hacked a module named Coro (short for coroutines, similar
but not the same as threads or perl's faked threads). After using it to
implement fake continuations (to make damian conway happy, if he ever
finds out) I thought let's give Event a try (no, not faked this time ;)
use Coro 0.
