Nicholas Clark wrote:
If you're adding before or after an existing named stage, the ambiguity is
to which one you mean. Except having now studied the PIR, I can see that
there isn't ambiguity, because it's all of them.
There's no test for this though. Hence why I didn't realise.
Good point.
attached a patch for fixing
* some things for parsing PASM instructions correctly
* minor updates to pir.pg
regards,
kjs
Index: languages/PIR/lib/pasm_args.pg
===
--- languages/PIR/lib/pasm_args.pg (revision 17016)
+++
# New Ticket Created by James Keenan
# Please include the string: [perl #41529]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41529
Running make test, this morning, one failing test was fixed, one (the
shootout)
Just working on bug-day tickets (especially since I'm the release-
manager this month :-)...
On Wed Jan 31 13:37:54 2007, [EMAIL PROTECTED] wrote:
The primary purpose of a MANIFEST in the repository is to tell you
which files out of the repository should be included in the
distribution.
On Thu Jan 18 18:28:05 2007, [EMAIL PROTECTED] wrote:
Running make test this morning, I got exactly one failure. Here's an
excerpt from the output of 'make test':
...
Just checking -- are you still seeing the failure for 'make test'?
Pm
[EMAIL PROTECTED] writes:
Clarification of coercion declarations and semantics.
+++ doc/trunk/design/syn/S13.pod Fri Feb 16 17:59:34 2007
+method postcircumfix:( ) (|$capture) {...}
+method postcircumfix:[ ] (|$capture) {...}
+method postcircumfix:{ } (|$capture) {...}
Author: larry
Date: Sat Feb 17 10:25:36 2007
New Revision: 13590
Modified:
doc/trunk/design/syn/S13.pod
Log:
inconsistency spotted by Smylers++
Modified: doc/trunk/design/syn/S13.pod
==
---
# New Ticket Created by Allison Randal
# Please include the string: [perl #41528]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41528
Leo suggests merging the 'init' and 'init_pmc' vtable entries into a
single
On Tuesday 13 February 2007 08:10, Jerry Gay wrote:
# New Ticket Created by Jerry Gay
# Please include the string: [perl #41498]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41498
CPAN doesn't like parrot's
On Thursday 15 February 2007 08:24, Matt Diephouse wrote:
If you wanted to send me some sample code that invoked both a normal sub
and a MultiSub, I'd certainly take a look. I'm pretty sure the whole idea
of invoke-able objects was never really thought out -- some of the logic in
Sub.invoke()
James Keenan wrote:
Okay. So (a) are people experiencing this on other OSes? (b) how do
we fix it?
This was a feature request submitted as a failing test. I've changed the
test to reflect current behavior in r17026, and submitted the feature
request as a separate ticket #41528.
Allison
On Thu Jan 11 09:58:32 2007, [EMAIL PROTECTED] wrote:
I've held off on applying it because Allison said we need a
deprecation cycle
for the name() - get_name() rename.
I've made a note in DEPRECATED.pod that the method is being renamed
(r17030). Go ahead and apply this patch immediately after
2. Parrot::Distribution contains a subroutine called is_perl() which
presumably tests whether a file in @perl_language_files actually *is* a
Perl file.
However, I cannot locate any location where is_perl() is called.
It used to be called deep in the bowels of Parrot::Distribution before
Two points in follow-up:
1. This bug has been difficult to diagnose because Parrot::Distribution
-- which is what it is ultimately testing -- names some variables in
ways that, IMHO, are misleading. Take, for example, this subroutine:
sub get_perl_language_files {
my $self = shift;
On Sat Jan 27 11:39:15 2007, [EMAIL PROTECTED] wrote:
This patch allows object vtable method overrides for find_method,
get_attr,
get_attr, get_attr_str, set_attr, set_attr_str, and get_class. Now these
can be overridden in PIR using the :vtable flag or prefixing their
respective names with
(This is with parrot built from the subversion trunk, revision 16999)
Here's a bit of PIR that demonstrates my problem:
.sub 'main' :main
load_bytecode 'dumper.pir'
.local ResizablePMCArray fields
split fields, ,, hey,you
_dumper (fields)
On 2/17/07, James E Keenan [EMAIL PROTECTED] wrote:
jerry gay wrote:
On 2/17/07, via RT James Keenan [EMAIL PROTECTED] wrote:
The file which is failing the test is a Parrot source file (which
happens to be a Parrot test file) -- not a Perl source file (which
happens to be a Perl test file).
On 2/17/07, Paul Cochrane [EMAIL PROTECTED] wrote:
2. Parrot::Distribution contains a subroutine called is_perl() which
presumably tests whether a file in @perl_language_files actually *is* a
Perl file.
However, I cannot locate any location where is_perl() is called.
It used to be called
On Sat, Feb 17, 2007 at 09:21:45AM -0800, Eric Hanchrow wrote:
(This is with parrot built from the subversion trunk, revision 16999)
Here's a bit of PIR that demonstrates my problem:
.sub 'main' :main
load_bytecode 'dumper.pir'
.local ResizablePMCArray fields
On Saturday 17 February 2007 08:42, Allison Randal via RT wrote:
On Thu Jan 11 09:58:32 2007, [EMAIL PROTECTED] wrote:
I've held off on applying it because Allison said we need a
deprecation cycle
for the name() - get_name() rename.
I've made a note in DEPRECATED.pod that the method is
20 matches
Mail list logo
