--- Melvin Smith <[EMAIL PROTECTED]> wrote:
> Burp, more spam from me...
And there was much rejoicing... (rah! yay!)
> As I see it there are several immediate questions to be
> answered for Parrot
> IO.
> Feel free to answer with Y/N or Maybe.
All of the above?
> 1) Nick Ing-Simmons' Perl IO f
On Tue, Dec 18, 2001 at 02:42:29PM -0500, Melvin Smith wrote:
These are my opinions. If Dan contradicts me, he wins.
> 1) Nick Ing-Simmons' Perl IO for Perl5
> a) Could it easily support the features that Dan wants in Parrot IO
> such
> as async stuff?
Yes.
> b) Does it rep
On Tue, Dec 18, 2001 at 10:26:26PM +0100, Marcus Petersson wrote:
> I wonder if it's possible to add your own custom opcodes yet. What I have
> in mind are ops for about 10 external functions.
I anticipated this question so well that you'll find the answer in
the middle of docs/intro.pod :)
--
At 10:26 PM 12/18/2001 +0100, Marcus Petersson wrote:
>Hi,
>
>I wonder if it's possible to add your own custom opcodes yet. What I have
>in mind are ops for about 10 external functions. AFAIK, there are at least
>four things that need to be added:
>
>1. The bytecode format need codes for the new o
Marcus writes:
>I wonder if it's possible to add your own custom opcodes yet. What I have
>in mind are ops for about 10 external functions. AFAIK, there are at least
>four things that need to be added:
>
>1. The bytecode format need codes for the new ops.
>
>2. The assembler format need names for
Marcus Petersson:
# I wonder if it's possible to add your own custom opcodes yet.
# What I have
# in mind are ops for about 10 external functions. AFAIK, there
For now, just add the desired ops to core.ops and rebuild Parrot; make
should Do The Right Thing. In the future it will be more complica
Dan says:
>'Kay, here's the thought. Exactly one filter may be (optionally) marked as
>an interpreter terminal filter. It runs in the context of the interpreter
>that made the I/O request, and gets (or returns) a real PMC. All the other
>filters run in the context of a separate interpreter, and wh
Hi,
I wonder if it's possible to add your own custom opcodes yet. What I have
in mind are ops for about 10 external functions. AFAIK, there are at least
four things that need to be added:
1. The bytecode format need codes for the new ops.
2. The assembler format need names for the new ops.
3.
At 03:55 PM 12/18/2001 -0500, Melvin Smith wrote:
> >> async (background thread or something) or just say, "tough!?"
> >
> >Emulate. And then I get to send out lots of cranky "Not async safe!"
> >messages when things break places with real async IO systems. :)
>
>*cough* These VMS bigots...
At 03:36 PM 12/18/2001 -0500, Melvin Smith wrote:
>Dan writes:
> >*) Filehandles get treated like arrays. Filters (which will be plain
> >coderefs) can be push/pop/shift/unshift/spliced onto them.
>
>By coderef I'm assuming you mean something like this Perl pseudo code...
>
>sub filter_dos_newlin
>> async (background thread or something) or just say, "tough!?"
>
>Emulate. And then I get to send out lots of cranky "Not async safe!"
>messages when things break places with real async IO systems. :)
*cough* These VMS bigots... :)
-Melvin Smith
IBM :: Atlanta Innovation Center
[EMAIL P
Dan writes:
>*) Filehandles get treated like arrays. Filters (which will be plain
>coderefs) can be push/pop/shift/unshift/spliced onto them.
By coderef I'm assuming you mean something like this Perl pseudo code...
sub filter_dos_newlines {
my $pmc = shift;
my $op = shift;
if( $
At 08:09 PM 12/18/2001 +, Alex Gough wrote:
>On Tue, 18 Dec 2001, Dan Sugalski wrote:
> > [BTW, I'm being horrible and replying to this on perl6-internals, since
> > it's important]
> > At 09:16 AM 12/17/2001 -0800, Brent Dax wrote:
> > >Dan Sugalski:
> > ># However, that's not appropriate her
All --
I just committed some performance-enhancing changes to the
predereferencing code path. The commit message follows after
some notes on the performance results here.
Without optimization:
Before the change:
./test_parrotexamples/assembly/mops.pbc --> 23.02
./test_parrot -P
On Tue, 18 Dec 2001, Dan Sugalski wrote:
> [BTW, I'm being horrible and replying to this on perl6-internals, since
> it's important]
> At 09:16 AM 12/17/2001 -0800, Brent Dax wrote:
> >Dan Sugalski:
> ># However, that's not appropriate here--set P0, P1 should just copy the
> ># pointer from P1 to
At 12:04 AM 12/15/2001 -0500, [EMAIL PROTECTED] wrote:
>Can we start some dialogue about stream filters?
>What form they take, are we talking regular expressions, etc.
Yes, we can. Here's what I'm thinking of.
*) Filehandles get treated like arrays. Filters (which will be plain
coderefs) can be
At 02:42 PM 12/18/2001 -0500, Melvin Smith wrote:
>Burp, more spam from me...
M, spam! With mustard and cheddar, on a toasted bagel! :)
>As I see it there are several immediate questions to be answered for Parrot
>IO.
>Feel free to answer with Y/N or Maybe.
>
>1) Nick Ing-Simmons' Perl IO fo
Burp, more spam from me...
As I see it there are several immediate questions to be answered for Parrot
IO.
Feel free to answer with Y/N or Maybe.
1) Nick Ing-Simmons' Perl IO for Perl5
a) Could it easily support the features that Dan wants in Parrot IO
such
as async stuff?
b)
[BTW, I'm being horrible and replying to this on perl6-internals, since
it's important]
At 09:16 AM 12/17/2001 -0800, Brent Dax wrote:
>Dan Sugalski:
># However, that's not appropriate here--set P0, P1 should just copy the
># pointer from P1 to P0. Actually stuffing the value of the PMC
># pointe
The instructions say to run "make parrot", but that won't work because
Configure.pl tells Makefile.in that the test program's name is
'test_parrot'. This tiny patch fixes that nit.
diff -r -u parrot/Configure.pl parrot-andy/Configure.pl
--- parrot/Configure.pl Fri Dec 14 20:39:40 2001
+++ parrot
Yes, thats what I was finding, the most basic Java stuff at least needs the
core
stream IO API which we don't have in Parrot yet. Have you considered
whether
it would be worthwhile to write a runtime Parrot -> JVM mapper
for classes that aren't translated (ie. any external method reference that
is
Melvin Smith sent the following bits through the ether:
> Anyone doing any work with Java bytecode to Parrot?
>
> I've got a java class disassembler 90% working if anyone is interested in
> helping, I'm not sure if this would belong in the Parrot tree or not.
Yes, actually. I've done some initi
Anyone doing any work with Java bytecode to Parrot?
I've got a java class disassembler 90% working if anyone is interested in
helping, I'm not sure if this would belong in the Parrot tree or not.
-Melvin Smith
IBM :: Atlanta Innovation Center
[EMAIL PROTECTED] :: 770-835-6984
"H.Merijn Brand" wrote:
>
> Changed 'make parrot' to 'make'
Yep. I had to change 'make parrot' to 'make' as well when compiling on
AIX 4.3
> AIX 4.3 --default:
>
> t/op/number.ok 7/28# Failed test (Parrot/Test.pm at line 76)
> # got: '5.00
> -0.00
> 2.00
> -
Changed 'make parrot' to 'make'
cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64-I./include -o interpreter.o -c interpreter.c
cc: "interpreter.c", line 160: warning 604: Pointers are not assignment-compatible.
and - for the smokes - please
# perl configure --default
:
:
Okay, we're done!
You can now use `make parrot' (or your platform's equivalent to `make')
to build your Parrot.
Happy Hacking,
The Parrot Team
l1:/pro/3gl/CPAN/parrot-current 104 > make parrot
perl vtable_h.pl
cc -DDEBUGGING -Ae -D_HPUX_SOURCE -I/pro/local/i
On Tue, Dec 18, 2001 at 02:14:04AM -0500, Jeff G wrote:
> Note the three-parameter set() ops, specifically.
> A little lacking in documentation, but they do indeed work.
Perfect. And the right way to do it, too. Good job.
> Does the current Perl6 licensing situation permit me to use the perl5
>
27 matches
Mail list logo
