Parrot 0.6.2 is on schedule for the 20 May release. In preparation, please
gather up any NEWS you find important for your subsystem, please report any
PLATFORMS updates, and please run make fulltest on every architecture you can
find.
I'd like to concentrate on applying patches and fixing bugs
On Fri, May 16, 2008 at 5:31 PM, Bob Rogers
<[EMAIL PROTECTED]> wrote:
> From: Jonathan Worthington <[EMAIL PROTECTED]>
> Date: Sat, 17 May 2008 01:38:46 +0200
>
> Bob Rogers wrote:
> > It is a good idea. I think I would call it ":class", though.
>
> I did ponder that, and then worried t
From: Jonathan Worthington <[EMAIL PROTECTED]>
Date: Sat, 17 May 2008 01:38:46 +0200
Bob Rogers wrote:
> It is a good idea. I think I would call it ":class", though.
I did ponder that, and then worried that people would confuse it with
putting a method into a certain class, wh
It could be a pmc instead of a class. How about :type ?
On Fri, May 16, 2008 at 7:38 PM, Jonathan Worthington
<[EMAIL PROTECTED]> wrote:
> Bob Rogers wrote:
>>
>> From: Jonathan Worthington <[EMAIL PROTECTED]>
>> Date: Sat, 17 May 2008 00:25:35 +0200
>>
>> Hi,
>>
>> In Perl 6 we need to be
Bob Rogers wrote:
From: Jonathan Worthington <[EMAIL PROTECTED]>
Date: Sat, 17 May 2008 00:25:35 +0200
Hi,
In Perl 6 we need to be able to have Parrot subs take on a range of
different types . . .
Is the idea sane, and is the name of the adverb OK? If so, I'll go ahead
On Fri, May 16, 2008 at 11:12:54PM +0100, Nicholas Clark wrote:
> On Fri, May 16, 2008 at 03:20:34PM -0500, Patrick R. Michaud wrote:
> > On Fri, May 16, 2008 at 09:12:19PM +0100, Alberto Simões wrote:
> > >if (!base && !(i && scale) && (!emit_is8bit(disp) || 1)) {
> > >
> > > This is exactly
From: Jonathan Worthington <[EMAIL PROTECTED]>
Date: Sat, 17 May 2008 00:25:35 +0200
Hi,
In Perl 6 we need to be able to have Parrot subs take on a range of
different types . . .
Is the idea sane, and is the name of the adverb OK? If so, I'll go ahead
and implement it (wit
On Friday 16 May 2008 16:56:13 Bob Wilkinson wrote:
> On Sat, May 03, 2008 at 04:14:27AM -0700, [EMAIL PROTECTED] wrote:
> > Modified: trunk/docs/pdds/pdd28_strings.pod
> > =
> >= --- trunk/docs/pdds/pdd28_strings.pod (o
On Sat, May 03, 2008 at 04:14:27AM -0700, [EMAIL PROTECTED] wrote:
> Author: allison
> Date: Sat May 3 04:14:26 2008
> New Revision: 27304
>
> Modified:
>trunk/docs/pdds/pdd28_strings.pod
>
> Log:
> [pdd] Strings PDD: fix a typo, move a few sections around.
>
>
> Modified: trunk/docs/pdds/
Hi,
In Perl 6 we need to be able to have Parrot subs take on a range of
different types. For example, those that are methods should be of type
Method, others of type Block, Submethod and so forth.
I'd like to propose a type adverb for subs.
.sub 'foo' :method :type('Submethod')
...
.end
On Fri, May 16, 2008 at 03:20:34PM -0500, Patrick R. Michaud wrote:
> On Fri, May 16, 2008 at 09:12:19PM +0100, Alberto Simões wrote:
> > Hi, Folks.
> >
> > There are a few files on the parrot source where the compiler complains
> > about a logic value that is always true.
> >
> > Let us check a
On Fri, May 16, 2008 at 09:12:19PM +0100, Alberto Simões wrote:
> Hi, Folks.
>
> There are a few files on the parrot source where the compiler complains
> about a logic value that is always true.
>
> Let us check a specific case:
>
> on src/jit_emit.h:231,
>
>if (!base && !(i && scale) &&
On Friday 16 May 2008 13:12:19 Alberto Simões wrote:
> There are a few files on the parrot source where the compiler complains
> about a logic value that is always true.
>
> Let us check a specific case:
>
> on src/jit_emit.h:231,
>
> if (!base && !(i && scale) && (!emit_is8bit(disp) || 1)) {
Hi, Folks.
There are a few files on the parrot source where the compiler complains
about a logic value that is always true.
Let us check a specific case:
on src/jit_emit.h:231,
if (!base && !(i && scale) && (!emit_is8bit(disp) || 1)) {
This is exactly
if (!base && !(i && scale)) {
N
Moritz Lenz moritz-at-casella.verplant.org |Perl 6| wrote:
S12 says (in the context of classes):
my method think (Brain $self: $thought)
(Such methods are completely invisible to ordinary method calls, and are
in fact called with a different syntax that uses ! in place of the .
character.
Kealey, Martin, ihug-NZ Martin.Kealey-at-vodafone.com |Perl 6| wrote:
In Java, "final" is used to denote both a *class* that can't change (extend),
and *value* that can't change (a constant member of the class).
Got it: on a value it means readonly.
--John
Brandon Allbery allbery-at-kf8nh.com |Perl 6| wrote:
S06/Lvalue subroutines: "Lvalue subroutines return a proxy object
that can be assigned to. (...)"
S13/Methods: "Setter methods that expect the new value as an argument
do not fall into the well-behaved category, however."
When I take the
That also fixes the bus error I reported in rt:
http://rt.perl.org/rt3/Public/Bug/Display.html?id=54004
I went ahead and closed that ticket out. jonathan++
Thanks!
chris
On May 16, 2008, at 7:01 AM, Jonathan Worthington wrote:
Chris Fields wrote:
There appears to be a possible GC-related b
Chris Fields wrote:
There appears to be a possible GC-related bug introduced to Parrot
prior to r27449 which is showing up in Rakudo. Using the following
script (courtesy of Jonathan W):
After investigating a little, the breakage occurred in:
http://www.parrotvm.org/svn/parrot/revision?rev=2
I wrote:
> > Overloading "final" was Java's rather inept attempt to
> > define objects with value semantics rather than container semantics
John M. Dlugosz <[EMAIL PROTECTED]> wrote:
> Can you tell me more about that, or point to something?
Alas I can't point to anything, it's just a personal c
S06/Lvalue subroutines: "Lvalue subroutines return a proxy object
that can be assigned to. (...)"
S13/Methods: "Setter methods that expect the new value as an argument
do not fall into the well-behaved category, however."
When I take these two together, in a way which may be out of contex
> -Original Message-
> From: chromatic [mailto:[EMAIL PROTECTED]
> We are trying to avoid the "java.lang.String is Final"
> problem here in various ways. One of them is not allowing
> library designers to mark things as final.
Overloading "final" was Java's rather inept attempt to def
# New Ticket Created by Geoffrey Broadwell
# Please include the string: [perl #54238]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=54238 >
The attached patch for OpenGL.pir and triangle.pir makes the following
changes:
1
and a few more thoughts:
I wrote:
> S12 says (in the context of classes):
>
>
> my method think (Brain $self: $thought)
>
> (Such methods are completely invisible to ordinary method calls, and are
> in fact called with a different syntax that uses ! in place of the .
> character. See below.
S12 says (in the context of classes):
my method think (Brain $self: $thought)
(Such methods are completely invisible to ordinary method calls, and are
in fact called with a different syntax that uses ! in place of the .
character. See below.)
And later on, in the context of roles:
my m
Moritz Lenz wrote:
While reading through actions.pm I found that method scope_declarator
wasn't very readable because it was very long.
A big part of that is the declaration of attributes which needs some
special handling.
The attached patch moves that code to a separate function called
declare
26 matches
Mail list logo
