jobs to run when the wall clock says they should be.
Something to keep in mind.
-- Rocco Caputo - http://poe.perl.org/
assembly.
1. B::Parrot
2. Parrot.xs
3. Providing opcodes for libperl functions and linking it in.
I haven't suggested asm(), so technically I'm safe. Right? :)
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
thread_new
set I1, read_log_entry
jsr thread_new
main_timer_loop:
set I1, main_timer_done
set I2, 1
jsr set_timer
return
main_timer_done:
jsr threads_active
ne I1, 0, main_timer_loop
end
__END__
-- Rocco Caputo / [EMAIL
on system threads can be tuned to
optimally spread execution across available CPUs. It could be as
small as 1 on single-processor systems that don't switch thread
contexts well.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
seems reasonable)
There probably isn't a huge amount to do with the thing--maintain macro
substitutions, handle local labels, manage sub definitions, and suchlike
things.
Anyone?
j0. I'll do it.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
--- assemble.pl-origFri Sep 14 11:20:05 2001
+++ assemble.pl Fri Sep 14 12:26:38 2001
@@ -59,7 +59,9 @@
# get opcodes from guts.
-open GUTS, interp_guts.h;
+open(GUTS, interp_guts.h) or
+ open(GUTS
Attached is a patch to assemble.pl that adds very simple macros. I
fear it's a bit of a hack, but I'm fighting my usual impulse to
rewrite stuff.
Attached is also macros.pasm, a simple usage case. It goes in t/ for
want of a better place, but it's not a true test yet.
-- Rocco Caputo / [EMAIL
-internals to tinker with. It's called phat, there is
some discussion about it in the list archive, and the working
prototype (for prototypical values of working) is still at
http://poe.perl.org/phat/phat.c.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
n
they're broadcast everywhere.
Apropos of Perl 5: I've experimented long and hard on the language
level in perl 5, and I have a test case for detect them without using
handlers. It's unreliable though. That is, it may miss duplicate
signals between checks. When is this an issue, though?
-- R
ponses as asynchronous callbacks.
I think that's it. Thank you for reading.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
ither threads OR async I/O are available.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
On Fri, 5 Jan 2001 23:46:33 -0500, Uri Guttman wrote:
"RC" == Rocco Caputo [EMAIL PROTECTED] writes:
RC With a tightly integrated event loop, blocking perl level I/O can be
RC implemented in terms of internal asynchronous I/O. An interpreter can
RC then block while perl is
-snapshot.tar.gz in that directory is a tarball of the whole
tree. Design notes are in Readme, the notes directory, and source
comments.
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
13 matches
Mail list logo
