HaloO,
David Green wrote:
On 2008-Oct-22, at 10:03 am, TSa wrote:
Note that types have a fundamentally different task in a signature
than name and position have. The latter are for binding arguments to
parameters. The types however are for selection of dispatch target.
Names do that too; I t
Chris (>):
> How safe is it today to pre-compile Rakudo code to PIR and expect that to
> behave identically to as if I compiled from .pm at runtime? I believe PCT
> is just generating PIR anyway, so my initial guess is that there should be
> no differences. Are there any gotchas, like compile-tim
# New Ticket Created by Chris Dolan
# Please include the string: [perl #60164]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60164 >
The attached one-line patch makes Rakudo's Test.pm methods (ok(), is
(), etc) return a b
# New Ticket Created by Vasily Chekalkin
# Please include the string: [perl #60168]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60168 >
Hello.
I've (slightly) refactor Junction.pir.
1. Get rid of "junction_comparision_
On Oct 27, 2008, at 3:07 AM, Carl Mäsak wrote:
Chris (>):
How safe is it today to pre-compile Rakudo code to PIR and expect
that to
behave identically to as if I compiled from .pm at runtime? I
believe PCT
is just generating PIR anyway, so my initial guess is that there
should be
no diffe
# New Ticket Created by Chris Dolan
# Please include the string: [perl #60160]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60160 >
The following simple test involves two .pm files that depend on each
other. In revisio
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Oct 27 13:00:01 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote:
> S05 always uses single curlies for closures, but throughout Parrot, code
> seems to use double curlies in PGE regexps. Why is that?
>
> That is, why this:
> m/ foo {{ say "found foo" }} /
> and not this:
> m/ foo { say "f
On Sun, Oct 26, 2008 at 11:17 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> Turns out setting the conditional breakpoint never fired; left this
> running overnight, and it eventually came back with the segfault
> directly. Back to the drawing board.
Here is a very small snippet of tcl (with a singl
# New Ticket Created by Vasily Chekalkin
# Please include the string: [perl #60166]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60166 >
Hello.
Exception handling in parrot doesn't unwind used stack frames.
Simple examp
# New Ticket Created by Will Coleda
# Please include the string: [perl #60170]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60170 >
While trying to duplicate the tcl segfault in PIR, I was able to
generate PIR that reliab
On Mon, Oct 27, 2008 at 12:14 PM, via RT Will Coleda
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #60170]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=60170 >
>
>
>
# New Ticket Created by Will Coleda
# Please include the string: [perl #60172]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60172 >
.sub _main
($S0) = 'blah'(:pir_only=>1)
.end
segfaults with:
0xb7e4fe84 in expand_pcc
HaloO,
Jon Lang wrote:
This can already be done, for the most part:
/ (<.does(ro)>) /
Mind you, this only searches a list; to make it search a tree, you'd
need a drill-down subrule such as I outline above:
/ <[>* (<.does(ro)>) <]>* /
Isn't it the case that ~~ has very special dispatch seman
On Mon, Oct 27, 2008 at 06:20:51PM +0100, TSa wrote:
> HaloO,
>
> Jon Lang wrote:
>> This can already be done, for the most part:
>>
>> / (<.does(ro)>) /
>>
>> Mind you, this only searches a list; to make it search a tree, you'd
>> need a drill-down subrule such as I outline above:
>>
>> / <[>* (<.
On Sun, Oct 26, 2008 at 02:47:12PM -0700, Carl Mäsak wrote:
>
> rakudo: if(3 < 5) { say "yes" } # that should fail
>
> Early experimentation indicates that this goes for unless, while,
> until and given as well, and probably others I can't think of now.
Just for the record (since the ticket doe
On Sun, Oct 26, 2008 at 09:37:36PM -0400, Bob Rogers wrote:
> .sub 'main' :main
> foo('Hello')
> .end
> .sub foo :multi(String)
> .param pmc s
>
> say s
> .end
> [...]
>Which brings us to an interesting question: How can you decide wha
On Mon, Oct 27, 2008 at 03:47:50AM -0700, Vasily Chekalkin wrote:
> I've (slightly) refactor Junction.pir.
>
> 1. Get rid of "junction_comparision_helper". Use "infix_junction_helper"
> instead.
> 2. In "infix" and "unary" junction helpers store original value in
> ResultHash to avoid stringific
On Sat, Oct 25, 2008 at 06:50:29AM -0700, François PERRAD via RT wrote:
>
> In fact, perl6.exe contains some dependencies on build tree.
> Just after a build, perl6.exe works :
This is a known item -- see line 32 of languages/perl6/README:
This binary executable feature is still somewhat exp
On Sat, Oct 25, 2008 at 10:52:13AM +0200, Moritz Lenz wrote:
> Chris Dolan wrote:
> > I stumbled across this issue while descending into a recursive Match
> > structure. Consider the following reentrant subroutine:
>
> You have just experienced this bug:
> http://rt.perl.org/rt3/Ticket/Display.
On Sun, Oct 26, 2008 at 01:00:03PM -0700, Carl Mäsak wrote:
> Rakudo r32141 can understand unspaces consisting of a backslash
> followed by whitespace, but not unspace consisting of only a
> backslash.
>
> $ ./perl6 -e 'my %h; %h{"key"} = "value"; say %h\ {"key"}' # works fine
> value
> $ ./perl6
On Sun, Oct 26, 2008 at 12:33:21PM -0700, Carl Mäsak wrote:
> Rakudo r32141 fails to accept undef as a value to typed variables.
>
> $ ./perl6 -e 'my Int $a = undef'
> Type check failed
> [...]
>
> Should work according to S02.
Yes, this is a bug in Rakudo. We're likely to be revising all of
as
On Mon, Oct 27, 2008 at 9:31 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 26, 2008 at 11:17 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> Here is a very small snippet of tcl
Attached is a PIR-only file (no tcl required) that triggers the same
GC-related segfault (tested in r32210)
--
Patrick R. Michaud wrote:
On Fri, Oct 24, 2008 at 12:18:40PM -0700, Allison Randal wrote:
(I suppose technically we should stop calling this a "stack trace" since
it's not a stack. But "return continuation chain trace" is just too
verbose.)
"backtrace"
Exactly the word I was looking for.
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Mon, 27 Oct 2008 13:32:02 -0500
On Sun, Oct 26, 2008 at 09:37:36PM -0400, Bob Rogers wrote:
>.sub 'main' :main
>foo('Hello')
>.end
>.sub foo :multi(String)
>.param pmc s
>
>s
On Monday 27 October 2008 19:26:31 Bob Rogers wrote:
> All true. But it's unfortunate that the Parrot type system considers
> "int" and "Integer" unrelated. As a result, MMD prevents autoboxing
> (when chromatic and I had expected otherwise).
I'm not sure it's the type system as much as it is P
On Monday 27 October 2008 19:36:58 chromatic wrote:
> I think I know how to promote primitive registers to their
> autoboxed PMCs in that function; Parrot's calling conventions should take
> care of the rest.
Fixed in r32211. All tests pass (including the TODO test I added for this).
-- c
From: chromatic <[EMAIL PROTECTED]>
Date: Mon, 27 Oct 2008 20:00:50 -0700
On Monday 27 October 2008 19:36:58 chromatic wrote:
> I think I know how to promote primitive registers to their
> autoboxed PMCs in that function; Parrot's calling conventions should take
> care of the re
Earlier, I sent in a patch for PGE to support S05-style single-curly
closures (RT#60186). The next thing I'm trying to do is to get this
to work:
./perl6 -e '"" ~~ m/:lang(Perl6) { say "hi" }/'
The PIR version works perfectly:
./perl6 -e '"" ~~ m/:lang(PIR) { say "hi" }/'
Out of the b
29 matches
Mail list logo
