Re: [svn:parrot] r20172 - trunk/src/ops

2007-07-24 Thread chromatic
On Tuesday 24 July 2007 21:50:55 Andy Lester wrote: > > What am I missing here? > > Because PMCNULL can be (PMC)NULL or it can be PMCNULL, a special non- > null variable. > > See how it's defined in the header. I thought we fixed it. Let's fix it. -- c

Re: [svn:parrot] r20172 - trunk/src/ops

2007-07-24 Thread Andy Lester
On Jul 24, 2007, at 9:43 PM, chromatic wrote: $1 = PMC_IS_NULL(ns) ? PMCNULL : ns; If PMC_IS_NULL(ns) -- if it's PMCNULL -- then return PMCNULL. Otherwise, return ns. That is, return exactly what you were going to return anyway. What am I missing here? Because PMCNULL can be

Re: [svn:parrot] r20172 - trunk/src/ops

2007-07-24 Thread chromatic
On Tuesday 24 July 2007 21:25:39 Andy Lester wrote: > On Jul 24, 2007, at 8:56 PM, chromatic wrote: > > I presume that the function always returns either PMCNULL or a > > NameSpace PMC, > > so checking if it's returned PMCNULL and returning PMCNULL in that > > case seems > > a little silly. > Bec

Re: [svn:parrot] r20172 - trunk/src/ops

2007-07-24 Thread Andy Lester
On Jul 24, 2007, at 8:56 PM, chromatic wrote: I presume that the function always returns either PMCNULL or a NameSpace PMC, so checking if it's returned PMCNULL and returning PMCNULL in that case seems a little silly. Because I'm trying to get all the C code to be NONNULL as much as pos

Re: [svn:parrot] r20172 - trunk/src/ops

2007-07-24 Thread chromatic
On Tuesday 24 July 2007 15:37:54 [EMAIL PROTECTED] wrote: > Modified: trunk/src/ops/var.ops > === >=== --- trunk/src/ops/var.ops   (original) > +++ trunk/src/ops/var.ops   Tue Jul 24 15:37:53 2007 > @@ -105,8 +105,8 @@

[perl #43321] [TODO] config/init/defaults.pm: Write unit tests

2007-07-24 Thread James Keenan via RT
The basic functionality has been unit tested in t/configure/102-init_defaults.01.t and ...02.t. Ticket cannot be closed until its dependencies are resolved.

[perl #43923] [TODO] Don't regenerate MANIFEST unnecessarily

2007-07-24 Thread James Keenan via RT
New files committed; patches applied in r20181.

Tcl Assertion failures

2007-07-24 Thread Will Coleda
As of r20160, Tcl was generating a lot of assertion errors, ala: src/inter_call.c:228: failed assertion `sig_pmc->vtable->base_type == enum_class_FixedIntegerArray' Turns out, this is directly attributable to runtime/hacks.pir - my attempt to store the results of compilation of tcl to pir a

[perl #44101] Parrot 0.4.14 fails: "src/pmc/object.c", line 153: void function cannot return value

2007-07-24 Thread via RT
# New Ticket Created by Andy Dougherty # Please include the string: [perl #44101] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44101 > As of version 0.4.14, parrot no longer builds for me with Sun's Workshop compiler on

[perl #44139] opcodes, warnings, and exceptions

2007-07-24 Thread via RT
# New Ticket Created by Jerry Gay # Please include the string: [perl #44139] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44139 > the api for opcodes needs review, especially with regard to the response to exceptional beh

Re: What I broke

2007-07-24 Thread Andy Lester
On Jul 24, 2007, at 8:43 AM, Andy Lester wrote: Here's what I know is broken because of changes I've made yesterday: t/compilers/imcc/syn/file.t 255 6528013 16 1-13 This is still broken, as is shootout (of course). t/library/test_builder_tester.t0 612 16 1-12 t/l

What I broke

2007-07-24 Thread Andy Lester
Here's what I know is broken because of changes I've made yesterday: t/compilers/imcc/syn/file.t 255 6528013 16 1-13 t/library/test_builder_tester.t0 612 16 1-12 t/library/test_more.t 0 658 106 1-58 t/op/string.t 5 1280 160

Re: [perl #44121] [BUG] What happened to tools/build/fingerprint_c.pl?

2007-07-24 Thread Jonathan Worthington
Will Coleda via RT wrote: This appears to be nothing more than someone forgetting to update MANIFEST. The file was checked in at least a few revs ago, it was then deleted. Geck, that was me last night. Sorry all. (For those wondering where fingerprint_c.pl is going, I'm working on implementing

[perl #44121] [BUG] What happened to tools/build/fingerprint_c.pl?

2007-07-24 Thread Will Coleda via RT
On Tue Jul 24 05:11:52 2007, ptc wrote: > On 24/07/07, via RT James Keenan at parrotcode.org> wrote: > > # New Ticket Created by James Keenan > > # Please include the string: [perl #44121] > > # in the subject line of all future correspondence about this issue. > > # http://rt.perl.org/rt3/Ticke

[perl #44125] [PATCH] Configure.pl: more consistent interface

2007-07-24 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #44125] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44125 > In Configure.pl, some function/method calls take $args as an argument. Other function

Re: [perl #44121] [BUG] What happened to tools/build/fingerprint_c.pl?

2007-07-24 Thread Paul Cochrane
On 24/07/07, via RT James Keenan <[EMAIL PROTECTED]> wrote: # New Ticket Created by James Keenan # Please include the string: [perl #44121] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44121 > This file is still listed in

[perl #44121] [BUG] What happened to tools/build/fingerprint_c.pl?

2007-07-24 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #44121] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44121 > This file is still listed in the MANIFEST in trunk, [parrot] 518 $ grep -n fingerpri