I now have all of $(O_FILES) run through the headerizer. Not all
files get their declarations put into .h files automatically, but
it's a start.
Now I have to work on all the unprotected pointers. If anyone is
looking for something to do, run "make headerizer" and protect the
pointers t
> Does the attached patch solve the problem?
>
Yes, it does. Thanks.
thanks to the hallway track at OSCON, some help from particle, and many
many tuits this weekend, mod_parrot now builds against parrot HEAD, and
all tests pass. i went on hiatus way back in 2006 to wait for parrot to
mature a bit, and it's amazing how much has changed since i last worked
with i
Additional patch to get simple test statistics, number failed,
different number of tests run vs planned.
Index: languages/perl6/Test.pm
===
--- languages/perl6/Test.pm (revision 20326)
+++ languages/perl6/Test.pm (working copy)
@@ -45
From: "Mehmet Yavuz Selim Soyturk" (via RT) <[EMAIL PROTECTED]>
Date: Sun, 29 Jul 2007 16:29:15 -0700
# New Ticket Created by "Mehmet Yavuz Selim Soyturk"
# Please include the string: [perl #44247]
# in the subject line of all future correspondence about this issue.
# http://
# New Ticket Created by "Mehmet Yavuz Selim Soyturk"
# Please include the string: [perl #44247]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44247 >
Calling a METHOD (declared in a pmclass) from PIR with :flat modifier
se
I applied a bandaid to this wound today in r20318, but the patient still
needs to be referred to a specialist.
The "deep recursion" noted in the error message came from this code in
lib/Parrot/Pmc2c/Pmc2cMain.pm:
for my $f (@files) {
my $class = $self->read_dump($f);
print "
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #44249]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44249 >
Code around the sticky variable inside of a condition bug, and
add the diag subroutine.
Author: rgrjr
Date: Sun Jul 29 18:12:48 2007
New Revision: 20332
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
+ The push_eh I syntax actually creates a continuation.
Modified: trunk/docs/pdds/pdd23_exceptions.pod
=
Author: chromatic
Date: Sun Jul 29 18:05:12 2007
New Revision: 20330
Modified:
trunk/docs/pdds/draft/pdd09_gc.pod
Log:
[PDD 09] Reduce some of the more blatant lies in the GC design notes.
Modified: trunk/docs/pdds/draft/pdd09_gc.pod
===
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #44231]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=44231 >
I first noticed this with the patch I posted for Test.pm. The
first test description ge
Resolved in r20317. Much warnings-related code could be deleted from
test because the underlying Pmc2c packages are no longer spewing warnings.
make a humble beginning on the tests for the Perl 6 metamodel, adding
a README for the work. This chooses the top-level names "Class" and "MetaClass"
for the names of the perl6 metamodel. API largely stolen from Class::MOP
Signed-off-by: Sam Vilain <[EMAIL PROTECTED]>
---
This was almost a dir
On Jul 28, 2007, at 11:32 PM, chromatic wrote:
I want to get rid of this flag, and move the special case of DOD
marking into
the mark() vtable entry. Here's a patch which accomplishes most of
this
(except for getting rid of the special case) and breaks Tcl's PMCs
spectacularly.
ORLY?
I'
14 matches
Mail list logo