Re: Why no "is ro"? (Re: Subroutine parameter with trait and default.)

2008-09-25 Thread Michael G Schwern
David Green wrote: > I bet we actually don't disagree much; I'm not really against "ro" -- > I'm just not against "readonly" because of its length. If I were > writing casually, I'd use "rw" and "ro"; formally, I'd use "read only" > and "read/write" (or even "readable and writable"). At an in-bet

Re: [perl #59184] Some fixes to split methods

2008-09-25 Thread Chris Davaz
Nope, that last one was it. Still waiting on a decision for how edge cases on limit are to be handled. On Thu, Sep 25, 2008 at 10:49 PM, Moritz Lenz via RT <[EMAIL PROTECTED]> wrote: > On Mon Sep 22 22:55:29 2008, cdavaz wrote: >> Grr.. wrong again sorry!! Forgot to remove the handle_count label.

Does colonpair notation produce a Bool or Int?

2008-09-25 Thread Patrick R. Michaud
Lines 46-52 of t/spec/S02-literals/pairs.t claims that the colonpair notation should produce a Bool instead of an Int: #?rakudo todo 'Adverbial pairs without should produce a Bool (not Int)' is f2(:a), "Bool", "':a' is a named"; #?rakudo todo '.() sub calls' is(f2.(:a),

[perl #59340] t/stm/runtime_4.pir segfaults on FreeBSD 7 (i386)

2008-09-25 Thread via RT
# New Ticket Created by Geraud CONTINSOUZAS # Please include the string: [perl #59340] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59340 > --- osname= freebsd osvers= 7.1-prerelease arch= i386-freebsd-thread-multi-64in

Re: [perl #59308] Test failures due to integer overflow

2008-09-25 Thread Patrick R. Michaud
Here's a patch that gets PCT to avoid generating the constants that IMCC can't handle, S03-operators/arith.t passes with this patch. (I'm not in a place where I can do a full spectest_regression, so I'm leaving the patch here for someone else to apply and test.) Pm Index: compilers/pct/src/PAST/C

Re: [perl #59308] Test failures due to integer overflow

2008-09-25 Thread Patrick R. Michaud
On Thu, Sep 25, 2008 at 02:01:22PM -0700, chromatic wrote: > On Thursday 25 September 2008 00:09:37 Moritz Lenz wrote: > > As of today (and r31404) Rakudo's 'make spectest_regression' produces > > compile time errors in three files, all of which are related to integer > > overflow. > > I suspect i

Re: [perl #59308] Test failures due to integer overflow

2008-09-25 Thread chromatic
On Thursday 25 September 2008 00:09:37 Moritz Lenz wrote: > As of today (and r31404) Rakudo's 'make spectest_regression' produces > compile time errors in three files, all of which are related to integer > overflow. > > To reproduce: > $ cd languages/perl6 > $ make spectest_regression > $ ../../pa

Re: perldoc doesn't use $(PERLDOC) in docs/Makefile

2008-09-25 Thread chromatic
On Thursday 25 September 2008 13:29:20 Dave Whipp wrote: > I was attempting to build parrot (0.7.1 release), but got a failure in > the docs directory because "perldoc" was not in my path. Looking at the > Makefile I see that it sets "PERLDOC := /perldoc", but > uses "perldoc" in a rule. I think t

Re: [perl #59336] [BUG] Parrot fails integer comparisons when integers are > 2^31 apart

2008-09-25 Thread NotFound
> I suspect the problem is that the integer "greater than" operation > is performing a subtraction between the two (signed long) values > being compared, but the result of the subtraction is outside of > the range of signed longs. Correct. Fixed in r31419 -- Salu2

[perl #59336] [BUG] Parrot fails integer comparisons when integers are > 2^31 apart

2008-09-25 Thread Patrick R. Michaud (via RT)
# New Ticket Created by Patrick R. Michaud # Please include the string: [perl #59336] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59336 > Code says it all: $ cat w.pir .sub main $P0 = new 'Integer' $P0 = 2147483

perldoc doesn't use $(PERLDOC) in docs/Makefile

2008-09-25 Thread Dave Whipp
I was attempting to build parrot (0.7.1 release), but got a failure in the docs directory because "perldoc" was not in my path. Looking at the Makefile I see that it sets "PERLDOC := /perldoc", but uses "perldoc" in a rule. I think this is due to: parrot-0.7.1/config/gen/makefiles/docs.in:37

[perl #59250] [BUG] MMD bug in FixedPMCArray.sort

2008-09-25 Thread Vasily Chekalkin via RT
Hello. This bug caused by "runops_args" which doesn't populcate interp->current_args which used in "mmd_arg_tuple_func" to calculate signature for MMD. -- Bacek.

Re: [perl #59250] [BUG] MMD bug in FixedPMCArray.sort

2008-09-25 Thread Patrick R. Michaud
On Thu, Sep 25, 2008 at 05:05:16AM -0700, Vasily Chekalkin via RT wrote: > This bug caused by "runops_args" which doesn't populcate > interp->current_args which used in "mmd_arg_tuple_func" to calculate > signature for MMD. chromatic has suggested that we should wait for the pdd27mmd branch to mer

[perl #59308] Test failures due to integer overflow

2008-09-25 Thread via RT
# New Ticket Created by Moritz Lenz # Please include the string: [perl #59308] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59308 > As of today (and r31404) Rakudo's 'make spectest_regression' produces compile time errors

[perl #50908] [CAGE] gcc -Werror=declaration-after-statement

2008-09-25 Thread Christoph Otto via RT
On Wed Sep 24 10:47:16 2008, cotto wrote: > On Mon Feb 18 18:07:43 2008, coke wrote: > > On Feb 18, 2008 8:39 PM, chromatic <[EMAIL PROTECTED]> wrote: > > > On Friday 15 February 2008 11:35:04 Will Coleda wrote: > > > > > > > According to http://gcc.gnu.org/onlinedocs/index.html#DIR, looks like > >

[perl #59288] [BUG] MMD bug in ResizablePMCArray.sort

2008-09-25 Thread via RT
# New Ticket Created by Vasily Chekalkin # Please include the string: [perl #59288] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=59288 > Hello. There is simple test case. $ cat mmd.pid .sub 'main' .local pmc arr

Re: Split with negative limits, and other weirdnesses

2008-09-25 Thread Chris Davaz
If someone wants to make the final word on what the behavior should be I can go ahead and implement it. On Tue, Sep 23, 2008 at 11:41 PM, Jonathan Scott Duff <[EMAIL PROTECTED]> wrote: > On Tue, Sep 23, 2008 at 9:38 AM, TSa <[EMAIL PROTECTED]> wrote: > >> HaloO, >> Moritz Lenz wrote: >> >>> In Per

Re: Revisiting lexicals, part 1

2008-09-25 Thread Geoffrey Broadwell
Tom Christiansen: > > Don't we have to solve all this to get the Perl 6 debugger > > working anyway? > > Although I'm unsure why that might be, I also recognize the possibility > that there may well exist hypothetical documents, unread by me, which > mandate some scenario or behavior wherein the