Re: [svn:parrot] r31049 - in trunk: include/parrot languages/perl6/src/builtins languages/perl6/src/parser languages/perl6/t

Patrick R. Michaud wrote: I'm not sure about this last comment -- I think I can imagine that other language implementations (including new ones we haven't thought of yet but suddenly becomes possible with Parrot) might want to make use of gather/take semantics if they're readily available -- e

Re: ExceptionHandler enhancement proposal

Bob Rogers wrote: Yes, once we have the ability to have exception handlers only handle specific types of exceptions, then they'll allow all other types of exceptions to pass through. (Which means we won't end up with the infinite exception handler loops we currently get if excepti

Re: How to define a new value type?

Ter, 2008-09-16 às 20:07 -0500, John M. Dlugosz escreveu: > Yes, with immutable objects you don't have to clone it. Multiple copies > can be shared. > By making "value types" as described above also immutable, it formally > removes all distinction between reference assignment and value assignmen

[perl #58952] Implemented second argument to comb

# New Ticket Created by "Chris Davaz" # Please include the string: [perl #58952] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58952 > Here is the implementation of the second argument to the comb method as described in S2

[perl #53536] [PATCH] sub-second sleep precision for non-threaded architectures

On Mon Sep 15 20:08:38 2008, [EMAIL PROTECTED] wrote: > chromatic wrote: > > On Monday 15 September 2008 01:25:15 Christoph Otto via RT wrote: > > > >> It applies with a little noise to the current trunk and passes make > >> test. The attached version just changes line numbers so the patch > >> ap

[perl #58866] calling a PIR sub with 206 params segfaults parrot

On Tue Sep 16 15:00:24 2008, [EMAIL PROTECTED] wrote: > On Tuesday 16 September 2008 14:47:58 NotFound wrote: > > > > It certainly shouldn't segfault. But, the question is: why does it > > > segfault at 206 parameters? Throwing an exception to avoid an > error we > > > don't understand isn't good

Re: [svn:parrot] r31049 - in trunk: include/parrot languages/perl6/src/builtins languages/perl6/src/parser languages/perl6/t

Not long ago, Patrick R. Michaud proclaimed... > I'm not sure about this last comment -- I think I can imagine > that other language implementations (including new ones we haven't > thought of yet but suddenly becomes possible with Parrot) might > want to make use of gather/take semantics if they'

[perl #58948] [BUG] multi subs compile but cause segfault

# New Ticket Created by "Stephen Simmons" # Please include the string: [perl #58948] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58948 > Using the more elaborate version of the testcase behind #58294, which has a two and

Should $.foo attributes without "is rw" be writable from within the class

Rakudo and I have a disagreement over this: I expect to be able to assign to a $.foo attribute in methods within the class, whereas Rakudo demands the "is rw" attribute in order to do that. We discussed it a bit on #perl6 today. I only have

Re: Should $.foo attributes without "is rw" be writable from within the class

Just to bring some of the IRC discussion to the list... Carl Mäsak wrote: > Rakudo and I have a disagreement over this: I expect to be able to > assign to a $.foo attribute in methods within the class, whereas > Rakudo demands the "is rw" attribute in order to do that. > > We discussed it a bit o

Re: Should $.foo attributes without "is rw" be writable from within the class

Moritz Lenz wrote: Yes, I know that $.stuff actually translates to $( self.stuff ), so without 'is rw' there is no rw accessor generated - but couldn't we just fake assignment to '$.foo' to actually affect '$!foo'? Why not just assign to $!foo, which is always read/write (since the rw affect

Re: Should $.foo attributes without "is rw" be writable from within the class

Jonathan (>): > Why not just assign to $!foo, which is always read/write (since the rw > affects whether you get an accessor that is read/write or not - $!foo refers > to the underlying storage location; at least, that's how I understand it and > what I think Rakudo is implementing today). I have

Re: How to define a new value type?

HaloO, Moritz Lenz wrote: When you read carefully through S29 you'll notice that most methods in immutable classes (like Str, List, Int) only return modified copies, even if they mutate the string in Perl 5. Great! (There are some exceptions like Str.substr, which explicitly 'is rw', and whi

Re: How to define a new value type?

TSa wrote: > The 'is rw' is on the method but I guess it is foreseen that the > result is stored in $string without preserving the identity of the > string? No. It means that the Str object has to get hold of the container in which it is stored, and store a modified copy in it. If that fails (for

[perl #58742] [TODO] Marker for RTs re SmartLinks

On Tue Sep 16 15:45:47 2008, [EMAIL PROTECTED] wrote: > > 2. I will apply a refined version of the patch. It will delete inline > comments referring to the deleted tickets. But I will leave to others > dealing with reference to smartlinks under languages/. Done, now that release has been cut.

Questions about :multi in Method Signatures

I am confused about how we should setup method signatures: Let's take a look at a line in any-str.pir: 46 .sub 'comb' :method :multi(_) 47 .param pmc regex 48 .param int count:optional 49 .param int has_count:opt_flag As you can see we have one parameter specified in

[perl #58958] Build of 0.7.1 fails with Intel compiler on Linux

# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #58958] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58958 > I'm trying to build Parrot 0.7.1 with Intel Compiler (see version information below

Re: [perl #58958] Build of 0.7.1 fails with Intel compiler on Linux

On Wednesday 17 September 2008 04:48:59 [EMAIL PROTECTED] (via RT) wrote: > src/exceptions.c(74): error: identifier "_CONST_STRING_74" is undefined >       VTABLE_set_integer_keyed_str(interp, exception, This one means that ICC handles #line directives differently. If you manually edit this lin

Re: Parrot 0.7.1 "Manu Aloha" released

Patrick R. Michaud a écrit : On behalf of the Parrot team, I'm proud to announce Parrot 0.7.1 "Manu Aloha." Parrot (http://parrotcode.org/) is a virtual machine aimed at running all dynamic languages. As usual, the Windows setup is available on http://parrotwin32.sourceforge.net/ François.

Re: [svn:parrot] r31049 - in trunk: include/parrot languages/perl6/src/builtins languages/perl6/src/parser languages/perl6/t

On Wed, Sep 17, 2008 at 10:57:31AM +0200, Allison Randal wrote: > Patrick R. Michaud wrote: >> >> I'm not sure about this last comment -- I think I can imagine >> that other language implementations (including new ones we haven't >> thought of yet but suddenly becomes possible with Parrot) might wa

Re: Questions about :multi in Method Signatures

On Wed, Sep 17, 2008 at 08:37:36PM +0800, Chris Davaz wrote: > I am confused about how we should setup method signatures: > > Let's take a look at a line in any-str.pir: > > 46 .sub 'comb' :method :multi(_) > 47 .param pmc regex > 48 .param int count:optional > 49 .param i

Re: [perl #58948] [BUG] multi subs compile but cause segfault

On Tue, Sep 16, 2008 at 09:01:06PM -0700, Stephen Simmons wrote: > Using the more elaborate version of the testcase behind #58294, which has a > two and a three argument version of max, what use to compile and execute > incorrectly before the bug fix now compiles and segfaults. I suspect this > ha

Re: [perl #58866] calling a PIR sub with 206 params segfaults parrot

On Tue, Sep 16, 2008 at 11:45 PM, Christoph Otto via RT <[EMAIL PROTECTED]> wrote: > On Tue Sep 16 15:00:24 2008, [EMAIL PROTECTED] wrote: >> On Tuesday 16 September 2008 14:47:58 NotFound wrote: >> >> > > It certainly shouldn't segfault. But, the question is: why does it >> > > segfault at 206 par

Re: How to define a new value type?

HaloO, Moritz Lenz wrote: TSa wrote: The 'is rw' is on the method but I guess it is foreseen that the result is stored in $string without preserving the identity of the string? No. It means that the Str object has to get hold of the container in which it is stored, and store a modified copy i

Re: [perl #58948] [BUG] multi subs compile but cause segfault

On Wed, Sep 17, 2008 at 10:01:12AM -0500, Patrick R. Michaud wrote: > On Tue, Sep 16, 2008 at 09:01:06PM -0700, Stephen Simmons wrote: > > Using the more elaborate version of the testcase behind #58294, which has a > > two and a three argument version of max, what use to compile and execute > > inc

Re: Questions about :multi in Method Signatures

That's a great response, thanks. Clears things up. One question, should be always be using _ for the invocant or should we try to restrict it? On Wed, Sep 17, 2008 at 10:52 PM, Patrick R. Michaud <[EMAIL PROTECTED]>wrote: > On Wed, Sep 17, 2008 at 08:37:36PM +0800, Chris Davaz wrote: > > I am con

Re: Should $.foo attributes without "is rw" be writable from within the class

HaloO, Carl Mäsak wrote: My complaint could be pithily summarized as "those are _my_, attributes, why can't I write to them?" Perhaps you should change your POV. The correct terminus technicus for the $.foo twigil variables is 'call the method' which nicely embeds attribute access into dispatc

Re: Questions about :multi in Method Signatures

On Wed, Sep 17, 2008 at 11:48:54PM +0800, Chris Davaz wrote: > That's a great response, thanks. Clears things up. One question, should be > always be using _ for the invocant or should we try to restrict it? I suggest always using _ for the invocant, at least for now. Pm

Re: Questions about :multi in Method Signatures

Patrick R. Michaud wrote: > On Wed, Sep 17, 2008 at 08:37:36PM +0800, Chris Davaz wrote: >> I am confused about how we should setup method signatures: >> >> Let's take a look at a line in any-str.pir: >> >> 46 .sub 'comb' :method :multi(_) >> 47 .param pmc regex >> 48 .param int count

Re: Chained Modifiers

On Mon, Sep 15, 2008 at 12:16:22PM +0200, Moritz Lenz wrote: : Chris Davaz wrote: : > I'm not sure if it's anywhere in the specs, but I was expecting to be able : > to do this: : > : > .say for =$in unless $foo; : : to quote http://perlcabal.org/syn/S04.html#Loop_statements : : :Looping statemen

[perl #58978] [TODO][IMCC] replace .result by .get_result

# New Ticket Created by Klaas-Jan Stol # Please include the string: [perl #58978] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58978 > as suggested by Allison, .result in a .begin/end_call sequence will be replaced by .ge

[perl #58976] [TODO][IMCC] .arg will be replaced by .set_arg

# New Ticket Created by Klaas-Jan Stol # Please include the string: [perl #58976] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58976 > as suggested by Allison, the .arg directive in a .begin_call/end_call statement will b

[perl #58970] Initial implementation of Str.split(Regex)

# New Ticket Created by "Chris Davaz" # Please include the string: [perl #58970] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58970 > I say "initial" because it didn't pass one of my tests. This might be due to regular ex

[perl #58974] [TODO][IMCC] replace .return in tailcall context by .tailcall

# New Ticket Created by Klaas-Jan Stol # Please include the string: [perl #58974] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58974 > as suggested by Allison, .return in a tailcall context, like this: .return foo() wi

[perl #58980] [TODO][IMCC] .return in a .begin/end_return will be replaced by .set_return

# New Ticket Created by Klaas-Jan Stol # Please include the string: [perl #58980] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58980 > As suggested by Allison, in a .begin/end_return sequence, the .return directive will b

Re: Should $.foo attributes without "is rw" be writable from within the class

On Wed, Sep 17, 2008 at 01:00:07PM +0200, Carl Mäsak wrote: : Jonathan (>): : > Why not just assign to $!foo, which is always read/write (since the rw : > affects whether you get an accessor that is read/write or not - $!foo refers : > to the underlying storage location; at least, that's how I unde

Re: Parrot 0.7.1 "Manu Aloha" released

http://www.parrotcode.org/release/devel still points to 0.7.0 -- Reini Urban http://phpwiki.org/ http://murbreak.at/

Re: [perl #58970] Initial implementation of Str.split(Regex)

Chris Davaz (via RT) wrote: > # New Ticket Created by "Chris Davaz" > # Please include the string: [perl #58970] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=58970 > > > > I say "initial" because it didn't pass one of

Re: Parrot 0.7.1 "Manu Aloha" released

On Wed, Sep 17, 2008 at 08:08:47PM +0200, Reini Urban wrote: > http://www.parrotcode.org/release/devel still points to 0.7.0 I sent the appropriate patch to the webmaster, but it hasn't been applied yet (and I lack a commit bit for the parrotcode.org site). Once that's applied, the url should be f

[perl #58990] [TODO] Design new spec coverage mechanism

# New Ticket Created by James Keenan # Please include the string: [perl #58990] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=58990 > We need a way to measure the extent to which Parrot's test suite covers the Parrot speci

[perl #58742] [TODO] Marker for RTs re SmartLinks

On Wed Sep 17 05:30:18 2008, [EMAIL PROTECTED] wrote: > > > > 4. I will then open up a new RT of the [RFC] class. This ticket will > > call for development of a specification of a way to visually display the > > extent to which Parrot's tests cover the specification. I'll be quoting > > from p

Re: Should $.foo attributes without "is rw" be writable from within the class

Carl Mäsak cmasak-at-gmail.com |Perl 6| wrote: I have come to understand that this is an available possibility, yes. That doesn't mean I like it. :) My complaint could be pithily summarized as "those are _my_, attributes, why can't I write to them?" // Carl If the accessor were implemented

Re: How to define a new value type?

TSa Thomas.Sandlass-at-vts-systems.de |Perl 6| wrote: Reading the description there I wonder how this is supposed to work. I don't think S29 is in any shape as a serious design specification. Maybe you should not design it that way. Maybe the left-hand-side is "as ref" so it can change the id

Re: How to define a new value type?

TSa Thomas.Sandlass-at-vts-systems.de |Perl 6| wrote: Sorry, I don't understand why you say 'no' and then explain that the resulting new string is stored in the container. The only container that could be affected by this is $string in the example. The way for a method to get access to the contai

Re: Should $.foo attributes without "is rw" be writable from within the class

Larry wrote: You have to have a way of talking about your own attributes *as if* they were not your own attributes, and $.foo is that way. When thinking about this, it's also important to remember that, in Perl 6, not everything with a sigil is automatically writeable. For example:

[perl #58970] Initial implementation of Str.split(Regex)

Ok, here it is without the change to "split on a string", and the test passes. Please apply this one and in the meantime I will see how we can get the method signature right for split on a strong + not break reverse. On Thu, Sep 18, 2008 at 1:57 AM, Moritz Lenz <[EMAIL PROTECTED]>wrote: > Chris