From: chromatic (via RT) <[EMAIL PROTECTED]>
Date: Sat, 10 Mar 2007 01:20:45 -0800
# New Ticket Created by chromatic
# Please include the string: [perl #41771]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id
Author: larry
Date: Sat Mar 10 21:59:07 2007
New Revision: 14330
Modified:
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S06.pod
Log:
More fiddling with context().
Modified: doc/trunk/design/syn/S04.pod
==
---
# New Ticket Created by Will Coleda
# Please include the string: [perl #41778]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41778 >
From docs/BROKEN.pod
No further information specified.
# New Ticket Created by Will Coleda
# Please include the string: [perl #41779]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41779 >
From docs/BROKEN.pod
No further information specified.
# New Ticket Created by Will Coleda
# Please include the string: [perl #41783]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41783 >
From docs/BROKEN.pod.
Is this something that needs fixing?
(it's in compilers/imcc/ma
# New Ticket Created by Will Coleda
# Please include the string: [perl #41782]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41782 >
from docs/BROKEN.pod
Leo suggests an eventual startup sequence of:
=over 4
=item * sta
# New Ticket Created by Will Coleda
# Please include the string: [perl #41781]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41781 >
from docs/BROKEN.pod
Give invokable PMCs a canonical way to store their associated HLL
s
# New Ticket Created by Will Coleda
# Please include the string: [perl #41780]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41780 >
From docs/BROKEN.pod
"chromatic has a test case almost ready to show this."
# New Ticket Created by Will Coleda
# Please include the string: [perl #41777]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41777 >
From docs/BROKEN.pod
No further information specified.
# New Ticket Created by Will Coleda
# Please include the string: [perl #41776]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41776 >
from docs/BROKEN.pod
=item * ParrotIO objects that work on strings
It should be possibl
Thanks, applied as r17431
Author: larry
Date: Sat Mar 10 16:02:36 2007
New Revision: 14329
Modified:
doc/trunk/design/syn/S06.pod
Log:
Whack in rethink of caller/context
Modified: doc/trunk/design/syn/S06.pod
==
--- doc/trunk/design/syn/S06.p
Larry Wall wrote:
On Sat, Mar 10, 2007 at 04:51:28PM +, Jonathan Worthington wrote:
: More interesting is that, for Perl 6,
: we also need to override the MRO on a by-method-call basis - you can
: change the dispatch order at the call site!
I wouldn't worry about that at all. I imagine s
On Sat, Mar 10, 2007 at 06:09:40PM +, Jonathan Worthington wrote:
: It's a confusing problem, for sure. I've thought about it, but as of yet
: have no good answers. I don't think forbidding having classes with
: different MROs in a single hierarchy is the answer, because that loses a
: lot o
On Sat, Mar 10, 2007 at 04:51:28PM +, Jonathan Worthington wrote:
: More interesting is that, for Perl 6,
: we also need to override the MRO on a by-method-call basis - you can
: change the dispatch order at the call site!
I wouldn't worry about that at all. I imagine such a construct
would
Nicholas Clark wrote:
On Sat, Mar 10, 2007 at 04:51:28PM +, Jonathan Worthington wrote:
Different languages may have a different MRO. Python since 2.3 and Perl
6 by default use C3. Perl 5 used something else. Therefore, we need
uses
Hope that thi
Author: larry
Date: Sat Mar 10 09:55:37 2007
New Revision: 14328
Modified:
doc/trunk/design/syn/S02.pod
Log:
further clarifications of substitution and reported string positions
Modified: doc/trunk/design/syn/S02.pod
===
James Keenan wrote:
I got errors in 5 different tests running 'make test' this morning on a
tree freshly updated from trunk. An excerpt from 'make test' output is
attached.
I mistakenly sent this first to [EMAIL PROTECTED], so I
think it didn't open a bug ticket in RT. I have re-sent it
# New Ticket Created by James Keenan
# Please include the string: [perl #41774]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41774 >
I got errors in 5 different tests running 'make test' this morning on
a tree freshly u
I got errors in 5 different tests running 'make test' this morning on
a tree freshly updated from trunk. An excerpt from 'make test'
output is attached.
Set aside the failure in t/perl/Parrot_Distribution.t; that's well
known. Here's the output of 'prove -v' on the other 4 files:
[parro
Author: larry
Date: Sat Mar 10 09:42:53 2007
New Revision: 14327
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarifications on StrPos and StrLen requested by putter++.
Modified: doc/trunk/design/syn/S02.pod
==
--- do
On Sat, Mar 10, 2007 at 04:51:28PM +, Jonathan Worthington wrote:
> Different languages may have a different MRO. Python since 2.3 and Perl
> 6 by default use C3. Perl 5 used something else. Therefore, we need
uses
> Hope that this makes some kinda sense - feed
Hi,
One of the things we need to specify in PDD 15 is method resolution order.
--
BACKGROUND
The MRO, short for Method Resolution Order, is the order in which we
search classes in an inheritance hierarchy when looking for attributes
or methods to call. The MRO is represented as a linearization
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #41772]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41772 >
hi,
attached a patch that adds a file languages/pynie/src/builtins/funcs.pir
providi
Author: audreyt
Date: Sat Mar 10 08:07:16 2007
New Revision: 14326
Modified:
doc/trunk/design/syn/S12.pod
Log:
* S12: Remove self-contractictory paragraph about indirect
object notation -- because the colon is needed regardless
of whether there are arguments after it -- and also
clarify
On Mar 9, 2007, at 10:42 AM, Will Coleda via RT wrote:
Do you still get the bug when you revert the change to Configure.pl?
This morning, I checked out a fresh version from trunk: r17419. I
ran myconfigure.sh, which internally called the HEAD version of
Configure.pl.
#!/bin/sh
Hi,
Here's a patch that does the minimal amount of work necessary to tell
ExtUtils::MakeMaker how to build Parrot::Embed from a compiled but
uninstalled Parrot. It works on Linux; my hope is that it will work much
better on Windows.
If it doesn't, it's because of one missing configuration ite
# New Ticket Created by chromatic
# Please include the string: [perl #41771]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41771 >
This code causes a segfault:
.sub test :main
get_results '(0)'
28 matches
Mail list logo
