Ovid wrote:
> - Original Message
>
>> From: Patrick R. Michaud
>
>> Source code repository
>> --
>> This is the immediate issue at hand, because we need to move Rakudo
>> out of the Parrot repository so that it can cleanly move to its new
>> home at parrot.org. Curr
# New Ticket Created by publiustemp-perl6compil...@yahoo.com
# Please include the string: [perl #62366]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62366 >
This patch implements die_on_fail (halts test at first test fail
Author: Whiteknight
Date: Wed Jan 14 16:44:41 2009
New Revision: 35571
Modified:
trunk/docs/pdds/pdd09_gc.pod
Changes in other areas also in this revision:
Modified:
trunk/include/parrot/pobj.h
trunk/src/gc/generational_ms.c
trunk/src/inter_call.c
trunk/src/pmc/deleg_pmc.pmc
Log:
Andy Bach writes (>):
> Hmm:
> ./perl6 -e 'my $x = :a<5>; say $x.map({.key, .value + 1}).perl'
> ["a", 6]
>
> ./perl6 -e 'my $x = :a<5>; say $x.map({.key => .value + 1}).perl'
> Method 'key' not found for invocant of class 'Failure'
>
> so it's the 'supercomma' that's troubled?
Seems like it. Th
On Wed Jan 14 22:00:33 2009, masak wrote:
> rakudo: my $t = 5; say $t.i
> rakudo 35576: OUTPUT«Method 'i' not found for invocant of
> class 'Int [...]
> TimToady: should that work?
> think so
> * masak submits rakudobug
Also this:
hmm
rakudo: my $t = 5; say $t\i
rakudo 35576: OUTPUT«Statem
Larry Wall wrote:
On Wed, Jan 14, 2009 at 09:55:38AM +0300, Richard Hainsworth wrote:
However, I came across one thing in solution #3 that I posted yesterday.
$pair.fmt("%s %s") is nice, but it doesnt allow for any action on either
value or key before printing (I wanted to print the value
# New Ticket Created by publiustemp-perl6interna...@yahoo.com
# Please include the string: [perl #62362]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62362 >
Test output:
t/library/protoobject.t . 8
# New Ticket Created by publiustemp-perl6interna...@yahoo.com
# Please include the string: [perl #62364]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62364 >
I tried to implement "plan *" for 'no_plan' and this is the min
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #62382]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62382 >
rakudo: my $t = 5; say $t.i
rakudo 35576: OUTPUT«Method 'i' not found for invocant of
Ovid (>):
> I tried to implement "plan *" for 'no_plan' and this is the minimal test case:
>
> perl6 $ perl6 -e 'my $plan = *; say $plan.isa(Whatever)'
> Method 'isa' not found for invocant of class 'Whatever'
> [...]
This has nothing to do with the bug, but you'd probably not want to
test for *-n
# New Ticket Created by mbere...@flashmail.com
# Please include the string: [perl #62376]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62376 >
in parrot/languages/perl6:
../../parrot perl6.pbc --target=pir --output=Test.p
- Original Message
> From: Patrick R. Michaud
> Many people have strongly suggested that we switch to
> using "git" as our version control system. At the moment I'm
> neither strongly in favor of nor strongly opposed to switching
> version control systems, but we have to recognize that
Ovid (>), Patrick (>>):
>> Many people have strongly suggested that we switch to
>> using "git" as our version control system. At the moment I'm
>> neither strongly in favor of nor strongly opposed to switching
>> version control systems, but we have to recognize that at least
>> two of Rakudo's "
# New Ticket Created by pancake
# Please include the string: [perl #62402]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62402 >
The 0.8.2 version of parrot crashes with this invalid perl6 oneliner:
./perl6 -e 'my @a; my
But doesnt Whatever smartmatch anything? Isn't that sort of its raison d'etre?
On 1/15/09, Carl Mäsak wrote:
> Ovid (>):
>> I tried to implement "plan *" for 'no_plan' and this is the minimal test
>> case:
>>
>> perl6 $ perl6 -e 'my $plan = *; say $plan.isa(Whatever)'
>> Method 'isa' not found
Mark (>), Carl (>>):
>> This has nothing to do with the bug, but you'd probably not want to
>> test for *-ness with .isa; use smartmatch (~~) instead.
>>
>> On the bright side, this already works in Rakudo:
>
> But doesnt Whatever smartmatch anything? Isn't that sort of its raison d'etre?
Short an
On Wed, Jan 14, 2009 at 10:02:21PM -0800, Carl Mäsak via RT wrote:
> On Wed Jan 14 22:00:33 2009, masak wrote:
> > rakudo: my $t = 5; say $t.i
> > rakudo 35576: OUTPUT«Method 'i' not found for invocant of
> > class 'Int [...]
> > TimToady: should that work?
> > think so
> > * masak submits raku
On Wed, Jan 14, 2009 at 10:00:33PM -0800, Carl Mäsak wrote:
> rakudo: my $t = 5; say $t.i
> rakudo 35576: OUTPUT«Method 'i' not found for invocant of
> class 'Int [...]
> TimToady: should that work?
> think so
> * masak submits rakudobug
Rakudo doesn't yet recognize the dotty form of postfix o
On Thu, Jan 15, 2009 at 12:46:09PM +0300, Richard Hainsworth wrote:
> Larry Wall wrote:
>> On Wed, Jan 14, 2009 at 09:55:38AM +0300, Richard Hainsworth wrote:
>>
>>> However, I came across one thing in solution #3 that I posted
>>> yesterday. $pair.fmt("%s %s") is nice, but it doesnt allow for
As outlined, the requirements seem to be pretty much those of any major
Open Source development project. Keeping this in mind might yield a
generic template usable by other projects in future.
Solving generic problems rather than specific ones does involve a little
more thought, (it's possible to
As a comment to my use.perl journal post, Infinoid wrote:
> Earlier today on the IRC channel, Will Coleda made an
> interesting comment regarding partcl.
>
> 07:28 <@Coke> I'd rather have folks go to /partcl/ to get parrot.
>
> That makes a lot of sense. So, have you given much thought to how
>
On Thu, Jan 15, 2009 at 1:32 PM, Andrew Whitworth via RT
wrote:
> Okay, I've committed a variant of my patch in r35599, but I've run into
> some issues while trying to test this. The morph VTABLE interface takes
> an INTVAL which represents the PMC type to morph to. This is the value
> that's pass
On Thu, Jan 15, 2009 at 6:32 PM, Andrew Whitworth via RT <
parrotbug-follo...@parrotcode.org> wrote:
> Okay, I've committed a variant of my patch in r35599, but I've run into
> some issues while trying to test this. The morph VTABLE interface takes
> an INTVAL which represents the PMC type to morp
# New Ticket Created by Jeff Horwitz
# Please include the string: [perl #62410]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62410 >
the Foo::bar() format for calling subs no longer works as of r35597. for
me personally
On Thu, Jan 15, 2009 at 04:20:28PM -, a...@ippimail.com wrote:
> As outlined, the requirements seem to be pretty much those of any major
> Open Source development project. Keeping this in mind might yield a
> generic template usable by other projects in future.
>
> Solving generic problems rat
On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
>
> Another thing to keep in mind is that once we start to have a Perl 6
> prelude, we might decide to be nice neighbors and share it with other
> implementations, as far as that's practical.
My guess is that there will be a shared pre
On Wed, Jan 14, 2009 at 11:57:02PM -0800, Ovid wrote:
> > From: Patrick R. Michaud
>
> What's the rationale for the spectest suite to remain in the
> pugs repository? AFAICT, pugs is no longer being actively
> developed and I wouldn't be surprised if many of its spectests
> currently break an
- Original Message
> From: Patrick R. Michaud
> Moritz already replied with why spectest is currently in pugs, I
> tend to agree. For now I'd like spectests to continue to have
> a very liberal commitbit policy, and that may or may not be
> compatible with Rakudo's commitbit policy (de
Patrick R. Michaud wrote (on p6c):
On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
Another thing to keep in mind is that once we start to have a Perl 6
prelude, we might decide to be nice neighbors and share it with other
implementations, as far as that's practical.
My guess is t
On Thu, 2009-01-15 at 16:03 -0800, Darren Duncan wrote:
> Patrick R. Michaud wrote (on p6c):
> > On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
> >> Another thing to keep in mind is that once we start to have a Perl 6
> >> prelude, we might decide to be nice neighbors and share it wit
Geoffrey Broadwell wrote:
The problem with this method is that there are usually *several* ways to
implement each feature in terms of some number of other features. The
creators of the shared prelude are then stuck with the problem of
deciding which of these to use. If their choices do not matc
On Thu, Jan 15, 2009 at 09:58:12AM -0600, Patrick R. Michaud wrote:
: On Wed, Jan 14, 2009 at 10:02:21PM -0800, Carl Mäsak via RT wrote:
: > On Wed Jan 14 22:00:33 2009, masak wrote:
: > > rakudo: my $t = 5; say $t.i
: > > rakudo 35576: OUTPUT«Method 'i' not found for invocant of
: > > class 'Int
On Thu, Jan 15, 2009 at 10:08:22AM -0600, Patrick R. Michaud wrote:
: On Wed, Jan 14, 2009 at 10:00:33PM -0800, Carl Mäsak wrote:
: > rakudo: my $t = 5; say $t.i
: > rakudo 35576: OUTPUT«Method 'i' not found for invocant of
: > class 'Int [...]
: > TimToady: should that work?
: > think so
: > *
Forgive my ignorance, but what is a Prelude?
--
Jonathan "Dataweaver" Lang
Jon Lang wrote:
Forgive my ignorance, but what is a Prelude?
The Prelude is a file written in Perl 6 that defines some Perl 6 built-ins.
See http://perlcabal.org/svn/pugs/view/src/perl6/Prelude.pm for what AFAIK is
the newest version.
-- Darren Duncan
On Thu, Jan 15, 2009 at 6:45 PM, Jonathan Scott Duff
wrote:
> On Thu, Jan 15, 2009 at 8:31 PM, Jon Lang wrote:
>>
>> Forgive my ignorance, but what is a Prelude?
>>
>> --
>> Jonathan "Dataweaver" Lang
>
> The stuff you load (and execute) to bootstrap the language into utility on
> each invocation
On Thu, Jan 15, 2009 at 8:59 PM, Jon Lang wrote:
> OK, then. If I'm understanding this correctly, the problem being
> raised has to do with deciding which language features to treat as
> primitives and which ones to bootstrap from those primitives. The
> difficulty is that different compilers p
Following some responses I've seen, I'll try to clarify my proposal. Basically
its like this.
A significant subset of Perl 6 native features, eg types and operators, native
meaning they are declared and described in the Perl 6 Synopsis documents, have
been implemented under Pugs by being writ
I'm re-working my "Periodic Table of the Operators" chart to be up-to-
date. I did the first major pass based on S03-operators. However,
the last few days I've been plowing through STD.pm and have discovered
that there some differences. Since STD.pm is considered more up to
date, I'll be
Mark Lentczner wrote:
> STD has sym<;> as both an infix operator ( --> Sequencer), and as a
> terminator.
> ?? Which is it? Since I think most people think of it as a statement
> terminator, I plan on leaving it off the chart.
It is both. Examples where it is used as an infix operator include:
Author: lwall
Date: 2009-01-16 08:42:00 +0100 (Fri, 16 Jan 2009)
New Revision: 24926
Modified:
docs/Perl6/Spec/S03-operators.pod
src/perl6/STD.pm
t/operators/adverbial_modifiers.t
t/run/02-dash-n.t
t/run/03-dash-p.t
Log:
[STD] alignment with S03 on associativity noted by mtnviewmark
41 matches
Mail list logo
