I'm about half-way through a quick classification of the failing PDD 15
tests (in t/pdd15oo). A number of the failures are quick things anyone
could pick off, so I'll share the list:
http://rakudo.org/parrot/index.cgi?pdd_15_remaining_features
We're only failing 157 out of 764 tests, so we're
On Tue, Jun 12, 2007 at 01:13:44PM -0700, Mark Glines wrote:
I just came up with an artificial benchmark and found that gcc-3.4.6
runs slightly faster with #pragma once protecting a header that includes
lots of other headers. (a chain of 200 other headers, in my test.) By
slightly, I mean
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #43187]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43187
I tried to build r18933 and received the following error message:
...
# New Ticket Created by Geraud CONTINSOUZAS
# Please include the string: [perl #43193]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43193
Description:
While reading the docs/parrotbyte.pod file with
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #43191]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43191
I tried to smoke r18926 on Solaris but failed because of tons of cannot
dereference
Applied in r18965.
kid51
On Jun 13, 2007, at 11:11 AM, [EMAIL PROTECTED] wrote:
Log:
Make 'headerizer' depend on 'fingerprint.c', so that
it can run right after 'make realclean; perl Configure.pl'
Thanks for doing this, Bernhard. I'm glad to have someone else
workin' w/me on the headerizer.
--
Andy Lester =
Look in src/objects.c, around line 80. This function looks up a vtable method
in a namespace. It has the name of the vtable method, as well as the number
of the vtable method.
Look how it reaches *inside* the namespace, grabs an iterator, and proceeds to
iterate through all of the keys of
On Wednesday 13 June 2007 12:45:12 [EMAIL PROTECTED] wrote:
Minor beautification in Parrot::Test
@@ -697,7 +694,7 @@
$builder-diag('$cmd' failed with exit code $exit_code)
if $exit_code and not $pass;
- unless ( $ENV{POSTMORTEM} ) {
+
chromatic writes:
On Wednesday 13 June 2007 12:45:12 [EMAIL PROTECTED] wrote:
Minor beautification in Parrot::Test
@@ -697,7 +694,7 @@
$builder-diag('$cmd' failed with exit code $exit_code)
if $exit_code and not $pass;
-unless ( $ENV{POSTMORTEM}
chromatic schrieb:
@@ -697,7 +694,7 @@
$builder-diag('$cmd' failed with exit code $exit_code)
if $exit_code and not $pass;
-unless ( $ENV{POSTMORTEM} ) {
+if ( ! $ENV{POSTMORTEM} ) {
unlink $out_f;
}
My patch only fails these tests.
Failed Test Stat Wstat Total Fail List of Failed
---
t/library/range.t 1 25678 18 70-78
t/pmc/parrotobject.t1 256111 3
Chromatic was right,
On Wednesday 13 June 2007 14:46:33 Kevin Tew wrote:
My patch only fails these tests.
Failed Test Stat Wstat Total Fail List of Failed
---
t/library/range.t 1 25678 18 70-78
On 6/13/07, Kevin Tew [EMAIL PROTECTED] wrote:
My patch only fails these tests.
this patch is better now that you added the case chromatic missed.
the location of the free_list segfault that perl6 experiences now
occurs when compiling the perl6 grammar, instead of when the test
suite was run.
chromatic wrote:
I wonder if changing the Namespace PMC to store all vtable methods in such a
way that an indexed lookup will work is a benefit. It might simplify the code
even further.
Yes, I'd like to see this. I did the groundwork for it already, by
refactoring the NameSpace PMC so
On Wednesday 13 June 2007 16:54:54 Jonathan Worthington wrote:
Yes, I'd like to see this. I did the groundwork for it already, by
refactoring the NameSpace PMC so that there is a place to hang such a
thing off now (just add it to the underlying struct), though I was doing
it so there was a
16 matches
Mail list logo
