Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
Examination of this file suggests that its length is simply a function
of the fact that PIR and PASM are mostly written with very short lines.
There is no compelling reason to try to subdivide the file. Closing
ticket.
On Wednesday 16 April 2008 15:39:41 Jonathan Worthington wrote:
> chromatic wrote:
> > It helps the PIR Ackerman benchmark by 4.67%. parrot_pass_args gets more
> > expensive, but next_arg_sig and everything else except for
> > Parrot_init_arg_indexes_and_sig_pmc gets called much, much less. I
>
chromatic wrote:
It helps the PIR Ackerman benchmark by 4.67%. parrot_pass_args gets more
expensive, but next_arg_sig and everything else except for
Parrot_init_arg_indexes_and_sig_pmc gets called much, much less. I played
with the patch a little bit, but didn't get it much faster.
So is t
Patrick R. Michaud wrote:
There's currently a problem in that
class Foo { }
doesn't create 'Foo' as a subclass of Object.
Hmmmthat's odd, since I can do:
class Foo { }
if Foo ~~ Object { say "yes" }
yes
if Foo.new() ~~ Object { say "yes" }
yes
I know that it doesn't explicitly do
Confirmed. This bug is still there as of r27009
"Nikolay Ananiev" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'll be able to test Parrot in the next 48 hours
> on my pentium mmx and tell you what the result is.
>
> - Original Message -
> From: "James Keenan via RT" <[E
On Wednesday 16 April 2008 10:49:15 Christoph Otto (Volt) wrote:
> The perl6 stand-alone binary chokes on chromatic's mmd example
> (http://www.oreillynet.com/onlamp/blog/2008/04/multiple_dispatch_now_please
>.html) under linux/x86. The bug was exposed in r26173, but the root cause
> is probably
# New Ticket Created by "Christoph Otto (Volt)"
# Please include the string: [perl #52976]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52976 >
The perl6 stand-alone binary chokes on chromatic's mmd example
(http://www.o
On Wed, Apr 16, 2008 at 1:49 PM, Mark Glines <[EMAIL PROTECTED]> wrote:
> On Wed, 16 Apr 2008 13:45:22 -0700
> "jerry gay" <[EMAIL PROTECTED]> wrote:
>
> > also, i'd like to automate more of the release process. currently, we
> > have a period of time where the link on the website for the most
>
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Wed, 16 Apr 2008 14:47:13 -0500
Also, something that might help with the discussion of multimethod
dispatch in rock-paper-scissors is to note that the mmd types do
not have to be directly related in the type hierarchy. In other
On Wed, 16 Apr 2008 13:45:22 -0700
"jerry gay" <[EMAIL PROTECTED]> wrote:
> also, i'd like to automate more of the release process. currently, we
> have a period of time where the link on the website for the most
> recent parrot will point to the previous release of parrot, until the
> new distro
one consistent trouble spot in the parrot release process is the CPAN
upload process. often times, we have trouble with perl modules that
have been added, deleted, or renamed causing the release to be marked
as 'unauthorized'. dealing with unauthorized releases involves
intervention from a pause ad
2008/4/15 jerry gay <[EMAIL PROTECTED]>:
> Aloha!
>
> On behalf of the Parrot team, I'm proud to announce Parrot 0.6.1
> "Bird of Paradise." Parrot (http://parrotcode.org/) is a virtual machine
> aimed
> at running all dynamic languages.
>
The Windows setup is available on http://parrotwin32.sour
On Wed, Apr 16, 2008 at 09:38:41PM +0200, Jonathan Worthington wrote:
> chromatic wrote:
> >You're right. I started from the wrong point in my bisect.
> >
> No worries.
>
> >I can't reproduce the problem with any revision before or after the 0.6.1
> >release.
> >
> But the 0.6.1 release had
chromatic wrote:
You're right. I started from the wrong point in my bisect.
No worries.
I can't reproduce the problem with any revision before or after the 0.6.1
release.
But the 0.6.1 release had a problem? If I'm understanding correctly, the
current revision doesn't show the problem?
On Wednesday 16 April 2008 11:22:08 Jonathan Worthington wrote:
> > This is the commit which broke the Rock, Paper, Scissors MMD example.
> *confused look* But I didn't implement the stuff needed to run the rock,
> paper scissors MMD example until 4 days after the commit you mention?
> http://par
chromatic wrote:
On Sunday 06 April 2008 16:05:45 [EMAIL PROTECTED] wrote:
Modified:
trunk/languages/perl6/src/builtins/guts.pir
trunk/languages/perl6/src/parser/actions.pm
trunk/languages/perl6/src/parser/grammar.pg
Log:
[rakudo] Add type-checking of parameters to subroutines and
On Sunday 06 April 2008 16:05:45 [EMAIL PROTECTED] wrote:
> Modified:
>trunk/languages/perl6/src/builtins/guts.pir
>trunk/languages/perl6/src/parser/actions.pm
>trunk/languages/perl6/src/parser/grammar.pg
>
> Log:
> [rakudo] Add type-checking of parameters to subroutines and methods.
On Wed, 2008-04-16 at 09:47 +0100, Tim Bunce wrote:
> I agree with Geoffrey that optimized builds should be the default.
Thank you!
> Developers working on parrot (wanting unoptimized/debug quick builds)
> would just need to set an env var in their .profile, for example, and
> carry on as now. N
# New Ticket Created by Will Coleda
# Please include the string: [perl #52956]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52956 >
While trying to put the macport for 0.6.1 together, I noticed that the
install failed.
T
Tim Bunce wrote:
I'd suggest a simpler approach than Geoffrey's: The default 'make'
target could default to a reasonably safe portable optimized target, but
be overridable by an env var.
[snip]
Developers working on parrot (wanting unoptimized/debug quick builds)
would just need to set an env
On Wed, Apr 16, 2008 at 12:10:54AM +0200, Leopold Toetsch wrote:
> Am Freitag, 11. April 2008 21:02 schrieb Nuno 'smash' Carvalho:
> > Greetings all,
> >
> > I just posted a little Parrot benchmark in my use.perl's journal
>
> Just a reminder:
>
> Please don't use unoptimzed builds for benchmark
35 matches
Mail list logo
