Re: merge event loops and threads (was Re: simple pointer operations (newbe))

Also sprach robic0:
On Mon, 6 Mar 2006 08:59:07 +0100, "Tassilo v. Parseval" <tassilo.von.parseval@xxxxxxxxxxxxxx> wrote:

Also sprach Uri Guttman:

i have an idea and most of the design for a module that will allow event
loops to work well with kernel (not perl!) threads that will run
blocking operations. of course it involves xs which i have done very
little with. would you (or anyone else) be interested in working on it
with (or for :) me? one variation on it (which could use this new module
or be its own module) would do true async file i/o and be synchronized
with the event loop. i have done such a beast before in pure c and it
worked very well. i think these modules are wanted and would be useful
to many event loop apps. imagine a simple api for async file i/o in perl
that was actually portable and bypasses all those wacko kernel aio apis
that each OS provides.

The specifications sound tempting although you didn't state how you'd
actually want to achieve the asynchronity when you avoid the existing
async IO mechanisms (of which each is unportable by nature). Does your
plan include rolling your own async IO scheme?

Also, I don't yet see how kernel threads come into this. Perl programs
don't have access to them other than through perl's ithreads.

Now wait a minute. Are you saying Perl programs "don't" have direct access
to the underlying OS api core?

I did not say this. Perl programs can be given access to whatever
interface the underlying operating system has to offer.

Well, how come? Apparently, Perl programs can do "pointer arithmatic".
Heh, where the *** does those docs exist?

You are talking gibberish. No one was talking about pointer arithmetic
in this thread. The topic was async IO and how to do it portably in
Perl.

So, the whole Perl thing is just a blow-me bull*** cover for really doing
C pointers. Well, holy GOD, why didn't they just say so. I could have used
any number of regex c-libs out there. Didn't know Perl was just a neo training
camp for the stupedist of C programmers. I didn't realize there was such a lack
of C/C++ (which is not the point), and of course the most important, a/the
OS Api.

The topic was async IO and how to do it portably in Perl.

Control and synchronization programming (blocking, etc) is a talent that you
can't just read-up on. Windows kernel, which provides "all" control programming
to user apps, uses "multiple blocking nomenclature and schem's", pseudo (name)
categories, hard/soft/level.

Once again: The topic was async IO and how to do it portably in Perl.

Who cares about the Windows kernel in this context?

You guys don't know your ass from your elbow!

You're well advised to just lurk if you have nothing to contribute which
you so seldom have.

Tassilo
--
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
.