On PASM and PIR registers

2007-01-31 Thread Klaas-Jan Stol
hello, Parrot has 2 categories of registers: PASM registers, which are of the form [S|N|I|P] (which is kinda odd, if only regs 0-31 are available) and PIR registers, which are formed like: $[S|N|I|P]+ In the old days, this distinction was necessary for the register allocator to translate PIR

Re: [svn:perl6-synopsis] r13550 - doc/trunk/design/syn

2007-01-31 Thread TSa
HaloO, Larry Wall wrote: ...I think that should work. The *-1 value just means "one before Whatever", and the dwim is, as you say, lazy. Or perhaps this generalizes to an odd form of currying: &replicate := * xx 42; Ohh, let me get that in my own words: the rhs replicates a Whatever int

Re: Whatever arithmetic

2007-01-31 Thread TSa
HaloO I wrote: my @a = 0,1,2,3,4,5,6,7,8,9; my $i = 5..*; say @a[$i]; # prints 5 6 7 8 9 And how about my $i = 5..*-1; say @a[$i]; # prints 5 6 7 8? The rational would be that the -1 goes into the range Whatever value, that is when it comes to expanding it inside the array

Re: Enhancing array indices

2007-01-31 Thread TSa
HaloO Larry Wall wrote: But maybe you meant @x[*+2 .. *-1]? And @x[*] would be @x[*+0..^*-0] written out that way. How far can we drive the dwimmy use of the three values that determine array access, i.e first and last index and length. E.g. would @x[*+0..*/2] roughly slice to the middl

Re: Enhancing array indices

2007-01-31 Thread TSa
HaloO, I wrote: E.g. would @x[*+0..*/2] roughly slice to the middle of the array? Hmm, this might not work. It should be @x[*+0..*-1-*/2] on the footing that the last * is dwiming the length. This implies that dispatches to &infix:<->:(Whatever, Whatever) and &infix:(Whatever,Int) are supporte

[svn:perl6-synopsis] r13557 - doc/trunk/design/syn

2007-01-31 Thread larry
Author: larry Date: Wed Jan 31 10:37:46 2007 New Revision: 13557 Modified: doc/trunk/design/syn/S05.pod Log: Clean up some of the language to avoid confusing automata terminology. Changed token keyword not to terminate token autodeclaration on whitespace, so it's now possible to specify a toke

[svn:perl6-synopsis] r13558 - doc/trunk/design/syn

2007-01-31 Thread larry
Author: larry Date: Wed Jan 31 13:01:12 2007 New Revision: 13558 Modified: doc/trunk/design/syn/S05.pod Log: Made a bunch of declarative/procedural distinctions. Modified: doc/trunk/design/syn/S05.pod == --- doc/trun

[perl #41386] MANIFEST must die.

2007-01-31 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #41386] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41386 > ... at least in the repository. The primary purpose of the MANFEST is to make sure that

[svn:parrot-pdd] r16859 - trunk/docs/pdds

2007-01-31 Thread allison
Author: allison Date: Wed Jan 31 14:26:06 2007 New Revision: 16859 Modified: trunk/docs/pdds/pdd22_io.pod Log: [pdd]: Questions and comments on I/O PDD from particle++ Modified: trunk/docs/pdds/pdd22_io.pod == --- tr

Re: [PATCH] PDD22 spec notes and ParrotIO tests

2007-01-31 Thread Allison Randal
Answering some questions from PDD 22. - On naming, let's go with a simple 'IO'. It's in the parrot namespace, so ['parrot';'IO']. IO is the base class, and may have other children such as ['parrot'; 'IO'; 'Socket'] (perhaps a role). - That said, I'll keep the text using more generic phrasing,

Re: [perl #41386] MANIFEST must die.

2007-01-31 Thread Allison Randal
Will Coleda (via RT) wrote: ... at least in the repository. The primary purpose of the MANFEST is to make sure that the generated release isn't missing any files, neh? So, when you're working out of the repository, you already know the canonical list. The primary purpose of a MANIFEST in th

Re: What Skills Do We Need to Finish Parrot?

2007-01-31 Thread Allison Randal
James E Keenan wrote: Do we have answers to the following questions? 1. What code is still unwritten that we will need to have Parrot ready to go (where "ready to go" is defined as: "ready for a Perl 6 alpha")? (I'll leave aside the question of when *that* will be ready.) The canonical list

[perl #41387] perlcritic.t picking up non-perl files

2007-01-31 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #41387] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41387 > The greatly improved Parrot::Distribution module (particle++) unfortunately now picks u

[perl #41388] Parrot::Distribution doesn't exclude all external perl modules

2007-01-31 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #41388] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41388 > Parrot::Distribution has a check for directories and files which are exempted from the

Re: What Skills Do We Need to Finish Parrot?

2007-01-31 Thread James Keenan
On Jan 31, 2007, at 4:48 PM, Allison Randal wrote: People with general experience in dynamic languages are also good: they pick up PIR quickly. Which leads to my next questions: Given a knowledge of a dynamic language (I believe there's one called Perl 5), what is the trajectory for l

Re: What Skills Do We Need to Finish Parrot?

2007-01-31 Thread chromatic
On Wednesday 31 January 2007 16:34, James Keenan wrote: > Which leads to my next questions: > > Given a knowledge of a dynamic language (I believe there's one called > Perl 5), what is the trajectory for learning PIR? Patrick and I talked about this a little bit today, though more in the context

Re: [PATCH] PDD22 spec notes and ParrotIO tests

2007-01-31 Thread jerry gay
On 1/31/07, Allison Randal <[EMAIL PROTECTED]> wrote: Answering some questions from PDD 22. thanks! all your edits are sane. - On naming, let's go with a simple 'IO'. It's in the parrot namespace, so ['parrot';'IO']. IO is the base class, and may have other children such as ['parrot'; 'IO'; '

PBC to C Converter

2007-01-31 Thread chromatic
Here's a quick Perl program that writes a C program that makes a self-contained executable for a Parrot program. I used as one example: $ parrot -o p8.pbc examples/japh/japh8.pasm $ perl pbc_to_c.pl j8.pbc > japh.c $ gcc -o japh japh.c -Iinclude -Lblib/lib -lparrot