On Feb 4, 2006, at 12:26, Leopold Toetsch via RT wrote:
Both on OS/X darwin and x86/linux 'make test' as well as
./parrot -p languages/punie/punie.pbc languages/punie/t/
problematic_1.p1
are succeeding here.
The error is gone here too now. Not sure if it's Leo's fix or unrelated.
Allison
On Feb 4, 2006, at 14:23, Joshua Isom via RT wrote:
Apparently I have a 267 megabyte past_node_5.out file... And if
past_op_2.pir and past_val_2.pir were printed to a file, I imagine
it'd
do the same(printing a lot of spaces). Seems to be more than just
Parrot::Test for me.
Could you
On Feb 4, 2006, at 16:51, Joshua Isom via RT wrote:
41 callmethodcc P1, dump -
P1=Object(PAST::Node)=PMC(0x50ba68),
102 get_params PMC_C[29] (2), P0, I0 - , P0=PMCNULL,
I0=5289976
106 repeat S0, , I0- , , I0=5289976
110 add I0, 1- I0=5289976,
On Feb 3, 2006, at 12:38, Nicholas Clark wrote:
This'll likely be out-of-date tomorrow, but I found it useful as a
quick snapshot/overview of the Parrot repository.
The process used to created it isn't amenable to automation into a
cron job?
It's just a Perl script, so yeah, could be
On Feb 2, 2006, at 15:10, Patrick R. Michaud via RT wrote:
...as of r11409, I'm not seeing the 'make test' error for punie
(on my Linux/x86_64 box).
I don't know if this is because it's now working, or because you've
routed around the particular problem you were seeing, so let
me know if
On Jan 31, 2006, at 16:26, Allison Randal wrote:
This'll likely be out-of-date tomorrow, but I found it useful as a
quick snapshot/overview of the Parrot repository.
http://www.lohutok.net/parrot.pdf (200k)
Sadly, it doesn't display in acrobat, but is fine in xpdf and
Preview.app
This'll likely be out-of-date tomorrow, but I found it useful as a
quick snapshot/overview of the Parrot repository.
http://www.lohutok.net/parrot.pdf (200k)
Allison
On Jan 17, 2006, at 18:01, Andrew Rodland wrote:
Doesn't that imply that print print print print 1; is a valid Punie
program? Is that intentional? It seems to me that the gprint rule
should instead contain cexpr:
rule gprint { (print) \s* PunieGrammar::cexpr }
print print print print 1;
I realize this is a side effect of the fact that method names are
actually strings, but it's an unfortunate result.
If I have a little bit of code that calls a method without quotes
around the name of the method, it calls the method (prints out
Boojum), exactly as expected:
.sub main
On Nov 29, 2005, at 15:08, Chip Salzenberg wrote:
Comments? Fresh or rotten vegetables?
My objections:
Consider:
P0 = P1
P0 = S1
P0 = I1
P0 = N1
o/~ One of these things is not like the others
One of these things just doesn't belong o/~
And if I have to read:
P0 =
On Nov 8, 2005, at 12:12, Joshua Hoblitt wrote:
Allison has an excellent document on the state of tool development in
her SVN tree. It would be nice to see it included with Parrot's
documentation.
It's still very rough, but will go into the Parrot repository after I
give it another pass
On Nov 5, 2005, at 19:37, Will Coleda (via RT) wrote:
Sending as a patch since 1) we're close to a freeze, and 2) this is
allison's code.
Allison: this patch fixes a dependency issue in the makefile,
eliminates some deprecation issues, and corrects a small issue in the
grammar that allows
I've been developing the tree transformation stuff outside the parrot
repository, and ran into some problems writing tests for my PIR
libraries. After talking to Chip Patrick, I'll be moving my code
into the parrot repository anyway, which scratches my immediate itch.
But, long-term it's
On Oct 17, 2005, at 12:26, Joshua Hoblitt wrote:
Does sticking Copyright The Perl Foundation at the top of a file
constitute a legal transfer of copyright?
No, there's no such thing as an implicit transfer of copyright rights.
Which is what I've been doing
but It's my understanding that
On Jul 14, 2005, at 12:51, Will Coleda wrote:
http://dev.perl.org/perl6/people.html
Perhaps we need a similar page on parrotcode. =-)
Seems unnecessary to maintain it in two locations, but you could link
to that one from parrotcode.org.
Ok. Does parrot/perl6 have a project planning tool?
On Jul 12, 2005, at 15:59, Will Coleda wrote:
Hey, Allison - you drafted up the project plan for TPF grant for
parrot, neh?
Yup. With a good deal of input from Dan, Leo, Patrick and others.
Are you the defacto Project Manager for parrot? Or is that position
unfilled?
Indeed I am. Parrot
On Jul 14, 2005, at 7:26, Will Coleda wrote:
MUahahahahaha, my trap has been sprung! Perfect. I've been looking for
you since before we lost Dan. =-)
Had I know this at the conference, I would have had a much longer
conversation with you. =-)
I can't say I've ever made any secret of the
On Jul 11, 2005, at 21:41, Autrijus Tang wrote:
Cool! However, I wonder if Punie is indeed targetting Perl 1.
As Schwern will attest, Perl 1 is a quite complicated language, with
nullary, unary, binary and ternary functions, arrays, hashes, pattern
matches, transliteration, format, loop
On Jul 12, 2005, at 0:37, Autrijus Tang wrote:
That's cool. In that case I'll commit the test suite from perl-1.0_16
as TODO tests to the Punie tree, if that's okay with you. :)
Most welcome. I'm following a naming convention in the t/ directory of
changing the original io.print-style file
On Jul 12, 2005, at 13:51, Will Coleda wrote:
Anyone have any ideas on how you might harness a PM group to work on
parrot?
Harness them to do what? Write tests? Clean up documentation? There's
certainly precedent (Phalanx), but you need a bunch of small,
achievable goals.
Allison
I'd like to add Punie to the Parrot repository. It's a first step
toward a compiler for Perl 1 running on Parrot. Currently it's *very*
simple: it only parses and compiles a single statement printing a
single digit -- but it uses PGE grammars and the stub in ast/ to do it.
Punie is a test
On Jul 3, 2005, at 7:42, Will Coleda wrote:
I was under the impression that for any code to be included in the
parrot repository, that the copyright had to be assigned to the Perl
Foundation. But there are exceptions to this throughout the
repository, even in core files like imcc/main.c
Alex Gutteridge wrote:
The example Perl6 'Game of Life' program
(parrot/languages/perl6/examples/life.p6) is broken. As it stands it
doesn't parse correctly but this is easily fixed by adding the correct
string concatenation operator '~':
I've checked in your update to the concat operator.
Leo wrote:
Fixed.
The code in smallobject.c that allocates new buffer memory did assume
that it gets zeroed memory, which of course depends on the OS and the
arena size. Now Cbuflen, which is used during GC, is cleared
explicitely.
Yup, that fixed it. Thanks!
Allison
Steve Fink wrote:
I suspect a slight variant of the above may work best. Rather than
doing a full-out LALR(1) parser for the bottom-up components, you'd do
a somewhat more naive but still table-driven (shift/reduce) parser,
carefully limiting what it is assuming about the FIRST() etc. of the
Abhijit A. Mahabal wrote:
On Mon, 10 May 2004, Steve Fink wrote:
use File::Basename qw(dirname);
use lib dirname($INC{P6C/Parser.pm})./../../../../lib;
I had already tried that, and it doesn't seem to work. I guess it is some
timing issue: $INC{P6C/Parser.pm} gets defined after
Dan Sugalski wrote:
I'm not so sure about that. (Not that it won't be replaced, but that
it needs the grammar engine) I'm pretty sure that grammars as Larry's
defined 'em are recursive-descent, and if that's true then I've this
really nasty feeling we're going to find it insufficiently
Dan Sugalski wrote:
Might not be out of line to start a notes file or something to throw
in observations and whatnot that you and other folks come across as
you work on this stuff.
I just added languages/perl6/doc/developer_notes.pod, with a few current
notes. Add to it as relevant.
Allison
Dan Sugalski wrote:
I think the first step here is to get the low-level perl operations
defined, and their parrot translations worked out. For this I mean
that we need to have a list of:
Perl:
a = b + c;
Parrot:
add a, b, c
I expect things like the foreach loops
Abhijit A. Mahabal wrote:
this is my first patch ever (not just p6i: ever). So do tell me
what I have done wrong.
Sorry not to respond before the patch was applied. Crazy week.
This is a patch for one of the ToDo items in languages/perl6/Todo. I have
updated the calling conventions in
Okay, languages/perl6 is failing all its tests.
The problem is in a few recent changes to lib/Parrot/Test.pm. The Perl
6 test module in languages/perl6/P6C/TestCompiler.pm inherits from
Parrot::Test, but overrides some subs. P6C::TestCompiler's
generate_pbc_for is writing the .pasm files in
Jerome wrote:
I'm sorry, I've been very busy for 2 weeks, and did not have the time to
continue things regarding this topic. :-(
I hope to have some more time this week-end, but I'm not even sure...
It happens. :)
So, very quickly:
1. The main goal is to have unified languages tests,
Dan wrote:
Well... the big problems we were make-related, with some tinder
issues. Basically if any test suite died really hard the testing
would stop, and only the last test suite run counted for tinder
good/bad reporting.
At this point, though, I'm comfortable making it so that any
Dan Sugalski wrote:
Applied. (Was there anything besides the /tmp change? That's all that
was in the attachment)
Calling 'rel2abs' was necessary so Parrot::Test would have the right
path to the test file later when it cd's to the main parrot directory
and calls './parrot'. That's all it
It's that time of year again, and we're looking for reviewers for the
2nd edition of Perl 6 Essentials. The review will start mid-March and
last about a week. Drop me a message if you're interested. We may have
to narrow down the list of volunteers a bit. 15 sets of comments is
about the maximum
I checked in some changes that allow up to 3 levels of hierarchy in the
languages/perl6 tests (t/harness, Makefile, and run_tests() in 'perl6').
I also added a few new test files that use the new levels of hierarchy.
This is the first step in moving toward the new test hierarchy:
Dan wrote:
Allison, if you've not gotten a perl.org account head over to
bugs.perl.org and get one so we can get you checkin privs. Seems
silly to force a go-between for updates to the perl compiler.
I'm allison.
Allison
Dan wrote:
Full CVS checkin, or would you prefer to stick with just the perl 6
section?
At the moment I don't expect to work on much outside the perl 6 section
except the Perl PMC's and occasional OS X patches. That may change.
shrug
Allison
Piers wrote:
p6d?
The perl6-documentation list. Started around Nov. 2002, it had about 3
months of heavy traffic and not much since. But, we did get a good plan
for the direction of p6 testing out of it.
Allison
Leo wrote:
I had a short look at the subdir hierarchy, looks good.
Excellent.
(perl6:run_tests, Makefile, and t/harness have to learn how to deal with
differently deep nested test files though).
Yeah, that's on my Todo list. Hmmm... I should probably add the list to
the repository.
If
Leo wrote:
I've added two test files, bitwise.t and concat.t, which go in t/op/
(the op/ directory doesn't exist yet)
Missing?
The directory needs to be added. We're gradually moving our way toward
the test hierarchy planned on p6d:
t/var
t/op
t/subs
t/regex
t/module
t/class
...
Or,
Leo wrote:
Very likely that SIGFPE isn't defined.
Does Fruntime/parrot/include/signal.pasm have an entry for SIGFPE?
(line 14)
.constant SIGFPE8
Is PARROT_HAS_HEADER_SIGNAL defined?
(Finclude/parrot/has_header.h: line 46)
define PARROT_HAS_HEADER_SIGNAL 1
Allison
Leo wrote:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/op/hacks.t2 512 22 100.00% 1-2
Could you please run these 2 standalone:
$ parrot t/op/hacks_1.pasm
catched it
error
On Tue, Dec 16, 2003 at 11:54:27PM -0500, Dan Sugalski wrote:
At 12:00 AM + 1/1/04, Allison Randal (via RT) wrote:
# New Ticket Created by Allison Randal
# Please include the string: [perl #24682]
# in the subject line of all future correspondence about this issue.
# URL: http
At 12:16 on 07/10/2003 PDT, Dan Sugalski [EMAIL PROTECTED] wrote:
At 11:56 AM -0700 7/10/03, Robert Spier wrote:
s/Yet Another Society/The Perl Foundation/g
The Perl Foundation is just a dba of YAS. The name should, unless
things have changed, be YAS.
We're generally encouraging the name
801 - 845 of 845 matches
Mail list logo
