Re: How to add new ops?

a PerlArray PMC commit today so maybe you could check out his patch or that crappy IO patch I posted a week ago. Start by looking at 'include/parrot/pmc.h'. Hope that helps, -Melvin Smith IBM :: Atlanta Innovation Center [EMAIL PROTECTED] :: 770-835-6984

Lack of responses

to it. Melvin Smith Centers for IBM e-business Innovation :: ATLANTA

Re: Lack of responses

Thats all the answer I was looking for. :) Melvin Smith Centers for IBM e-business Innovation :: ATLANTA (Embedded image moved to Dan Sugalski [EMAIL PROTECTED

IO/Shared mem api

Do we wish to abstract shared mem behind a Parrot IO object as well, so all the file methods work? Melvin Smith Centers for IBM e-business Innovation :: ATLANTA

IO call names

Would we prefer to leave the current system call names as-is (open,close read,seek) as the direct call through versions and name the IO routines pio_open, ... or go the route of Perl and do sys_open, etc. for the raw system call versions and name the Parrot IO API as the default names

Re: Parrot FAQ

A: VMS' QIO system. Sorta. Its been years since I worked on VMS. QIO is sorta async-IO, no? Can someone point me to some starting material for QIO and/or unimplemented wants/wishes for Parrot's IO sybsys? I might like to wade in in this area. I'll also start looking thru the archive. Melvin

Resend - PATCH: test_prog -d flag

Yipes lemme resend that, I was dinking around with a new mailer and it blew the tab formatting. -Melvin add_debug1.patch Description: unknown/unknown

interpreter-flags

Guys/Dan/Simon, While messing around tonight I noticed that interpreter flags aren't visible to any subsystem initialization code because the flags are passed to runops() instead of make_interpreter(). (I'm playing with some IO stuff and I'd like access to the flags at the time of the init code

Re: interpreter-flags

Correction, they aren't physically passed to runops() but you get the idea.. -Melvin ---Original Message--- From: Melvin Smith Date: Wednesday, December 05, 2001 08:49:30 PM To: [EMAIL PROTECTED] Subject: interpreter-flags Guys/Dan/Simon, While messing around tonight I noticed

PATCH

This patch fixes a infinite loop ('./test_prog --' for example) in the switch handling in test_prog and also modifies make_interpreter() to pass interpreter flags as constructor argument. -Melvin pass_flags.patch Description: unknown/unknown

My first parrot install - make test

. Finally Failed 8/8 test scripts, 0.00% okay. 112/115 subtests failed, 2.61% okay. make: *** [.test_dummy] Error 2 [root@cpan parrot]# I can see that core.pm doesn't exist under Parrot/OpLib but where to go from here; am I missing another module? Melvin Smith

<    1   2   3   4   5   6