# New Ticket Created by Will Coleda
# Please include the string: [perl #56786]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56786 >
Using tcl, I can make parrot segfault in this branch.
$ ../../parrot tcl.pbc -e "error e
On Wednesday 09 July 2008 12:03:19 chromatic wrote:
> On Wednesday 09 July 2008 08:27:35 Andrew Johnson wrote:
> > Confirmed, those warnings have gone. I'm still getting loads of
> > "warning: statement not reached" but I'll work out how to suppress those
> > and post a fix separately.
>
> Does yo
# New Ticket Created by NotFound
# Please include the string: [perl #56750]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56750 >
This patch adds a function to create empty strings, and replaces with
it a lot of CONST_STRI
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #56782]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56782 >
Hi,
in 'runtime/parrot/library/Getopt/Obj.pir' I saw the comment:
# XXX shou
# New Ticket Created by Will Coleda
# Please include the string: [perl #56792]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56792 >
New ticket opened from comment on list in thread 'Re: Warnings on
Solaris, Pmc2c usage/de
On Wed, Jul 9, 2008 at 9:33 PM, Andrew Johnson <[EMAIL PROTECTED]> wrote:
> The other warnings I get on Solaris are just these:
>
> "src/stm/backend.c", line 969: warning: statement not reached
> "./src/pmc/nci.pmc", line 486: warning: statement not reached
> "src/encodings/utf16.c", line 326: war
I've just committed a change (r29239) to allow Rakudo to build and run the
basic tests on the pdd25cx branch. Most of it works.
Test Summary Report
---
t/01-sanity/05-sub (Wstat: 256 Tests: 2 Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned
On Thu, Jul 10, 2008 at 1:25 PM, chromatic <[EMAIL PROTECTED]> wrote:
> I've just committed a change (r29239) to allow Rakudo to build and run the
> basic tests on the pdd25cx branch. Most of it works.
New Revision: 29239
Modified:
branches/gsoc_pdd09/languages/perl6/src/classes/Scalar.pir
EW
On Thursday 10 July 2008 10:29:16 Will Coleda wrote:
> On Thu, Jul 10, 2008 at 1:25 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > I've just committed a change (r29239) to allow Rakudo to build and run
> > the basic tests on the pdd25cx branch. Most of it works.
>
> New Revision: 29239
>
> Modified
# New Ticket Created by Will Coleda
# Please include the string: [perl #56798]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56798 >
Since the NQP tests aren't run by default, ran them by hand in pdd25cx:
Test Summary Rep
# New Ticket Created by Will Coleda
# Please include the string: [perl #56800]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56800 >
Meta ticket to track all the issues associated with this branch and
its eventually merge
On Thu, Jul 10, 2008 at 7:44 PM, Andrew Johnson <[EMAIL PROTECTED]> wrote:
>> Except the src/pmc/nci.pmc line 486, there is not such line in the
>> file, and I'm unable to locate the problem.
>
> If you look in the generated src/pmc/nci.c file at line 486, it has a #line
> directive that purports
# New Ticket Created by Will Coleda
# Please include the string: [perl #56804]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56804 >
The following tests fail during 'make test' on feather in the pd25cx branch.
Test Summar
# New Ticket Created by Will Coleda
# Please include the string: [perl #56806]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56806 >
pynie's test suite fails with [EMAIL PROTECTED]
Test Summary Report
---
On Thu, Jul 10, 2008 at 11:20:44AM -0700, Will Coleda wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #56806]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=56806 >
>
>
> pynie's test s
Will Coleda (via RT) wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #56756]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56756 >
On a win32 build with AS perl and the MS tools, I get the f
After some discussion on irc, rejected, it only hides problems.
On Thursday 10 July 2008 13:12:41 NotFound wrote:
> On Thu, Jul 10, 2008 at 7:44 PM, Andrew Johnson <[EMAIL PROTECTED]> wrote:
> >> Except the src/pmc/nci.pmc line 486, there is not such line in the
> >> file, and I'm unable to locate the problem.
> >
> > If you look in the generated src/pmc/nci.c
Applied in r29250
Reworked and committed with r29255.
$ prove -v t\pmc\io.t
t\pmc\io
1..45
not ok 1 - IO on some invalid types # TODO IO on some invalid types
# Failed (TODO) test 'IO on some invalid types'
# at t\pmc\io.t line 38.
# Exited with error code: 1
# Received:
# Undef ok 1
# Undef ok 2
# UndefCa
On Thursday 10 July 2008 10:44:51 NotFound wrote:
> On Wed, Jul 9, 2008 at 9:33 PM, Andrew Johnson <[EMAIL PROTECTED]> wrote:
> > The other warnings I get on Solaris are just these:
> >
> > "src/stm/backend.c", line 969: warning: statement not reached
> > "./src/pmc/nci.pmc", line 486: warning: sta
Applied with r29249. Thanks for your comments, chromatic++.
Ron
I changed the signature from PMC * to const PMC * in r29253, otherwise
using it with const gives warings in C and fails in C++.
What is the reason to have an interp parameter? Looks like an
unnecessary overhead in a frequently used function.
--
Salu2
# New Ticket Created by Andrew Whitworth
# Please include the string: [perl #56810]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56810 >
I found this while tracking a nasty GC-related bug. In
src/packfile/pf_items.c:PF_fe
On Thursday 10 July 2008 14:41:50 NotFound wrote:
> I changed the signature from PMC * to const PMC * in r29253, otherwise
> using it with const gives warings in C and fails in C++.
>
> What is the reason to have an interp parameter? Looks like an
> unnecessary overhead in a frequently used functi
On Wed Jul 02 09:17:44 2008, [EMAIL PROTECTED] wrote:
> On Wed Jul 02 06:25:14 2008, particle wrote:
> >
> > therefore, in an attempt to keep bytecode compatible across versions
> > of parrot, opcodes can never be deleted. instead, if opcodes are
> > deprecated, their function bodies should throw
Added some tests to t/steps/auto_opengl-03.t for internal subs
_evaluate_cc_run() and _handle_glut(). No need to do any refactoring of
step class itself. Test coverage is very high, so this ticket is
quickly being resolved.
BTW, japhb++ for instructions as to how to install Debian packages
neede
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #56816]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56816 >
There are a couple of issues with PMCProxy:
1. The PMCProxy returned from a get_
What's this branch for, out of curiosity?
--
Will "Coke" Coleda
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Thu, 10 Jul 2008 00:31:53 -0500
On Thu, Jul 10, 2008 at 12:29:57AM -0400, Bob Rogers wrote:
. . .
> Shouldn't
>for 1..10 -> $x {
> sub foo() { say $x; }
> push(@foos, \&foo);
>}
> produce the sam
On Thursday 10 July 2008 17:33:23 Patrick R. Michaud (via RT) wrote:
> There are a couple of issues with PMCProxy:
>
> 1. The PMCProxy returned from a get_class opcode isn't
> the same as one obtained from using typeof on an instance
> of the type.
>
> 2. Each invocation of typeof return
On Thu, Jul 10, 2008 at 09:35:29PM -0400, Bob Rogers wrote:
> Hmm. I have been assuming that when you say "taking a closure", that is
> equivalent to "using *the* closure" for a given :outer context. It's
> beginning to dawn on me that this might not be what you mean; more
> below.
I think I'm n
On Thu, Jul 10, 2008 at 06:50:51PM -0700, chromatic wrote:
>
> Here's a first approach. It breaks a couple of tests, but it's a start:
>
> t/pmc/object-meths (Wstat: 1280 Tests: 37 Failed: 5)
> Failed tests: 1-4, 16
> t/oo/proxy (Wstat: 256 Tests: 5 Fai
On Thu, Jul 10, 2008 at 09:51:40PM -0500, Patrick R. Michaud wrote:
> Perl 6 disallows having multiple subs of the same
> name unless they are explicitly declared 'multi' or
> the later subs provide the "is instead" trait [1].
Oops, I cut off the reference while sending:
[1] http://dev.perl.org/p
From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Thu, 10 Jul 2008 21:51:40 -0500
On Thu, Jul 10, 2008 at 09:35:29PM -0400, Bob Rogers wrote:
. . .
> [...] However, if some
> or all of these references were "downward" (i.e. not referenced after
> the containing block retur
On Thu, Jul 10, 2008 at 11:23:03PM -0400, Bob Rogers wrote:
>All I'm really wanting to know is what
>PIR the compilers and tools should be emitting for these very
>common Perl 6 constructs, and to have that PIR work in Parrot.
>
> Seriously, though, I've been wanting to learn more abou
On Thu, Jul 10, 2008 at 11:06:55PM -0500, Patrick R. Michaud wrote:
>
> I _think_ [methods and subs] are the only two cases where we
> have to do something like this, and I guess they aren't too onerous.
I was wrong, the third case is MultiSubs, and at the moment
it's _very_ onerous, because w
37 matches
Mail list logo
