On Monday 25 December 2006 21:44, James Keenan via RT wrote:
A few style comments here.
> Utils.pm
> unshift @{$allargsref->{include}}, (
> ".",
> "$FindBin::Bin/../..",
> "$FindBin::Bin/../../src/pmc/"
> );
Why no File::Spec here?
> if (File::Spec->file_nam
Here's a patch to implement get_name(), as specified in PDD 21. I haven't
checked it in because it includes an API change. There was already a name()
method in namespaces; I renamed it per the PDD.
-- c
=== src/interpreter.c
==
-
There is a repeatable segfault when GC is triggered during argument
passing after a tailcall. The immediate symptom is that clone_key_arg
blows cookies because the current arg is a 0xdeadbeef PMC. Apparently,
the sweep doesn't see pointers in the old context. The attached patch
(break-arg-pas
This patch makes pdump's output about debug segment more consistent:
before patch:
BYTECODE_/tmp/t.pir_DB => [ # offs ..., size 33, ... mappings => [
after patch:
BYTECODE_/tmp/t.pir_DB => [ # offs ..., size 33, ...
mappings => [
$ diffstat /tmp/packfile.patch
packfile.c |4 ++--
1 files
Applied as r16239, thanks!
Pm
# New Ticket Created by "Nikolay Ananiev"
# Please include the string: [perl #41132]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41132 >
Check the attached examples.
forgot to attach the files. Attached in this message.
test.pir
Description: Binary data
#include
#include
#include
Parrot_STRING pw_new_string(Parrot_Interp interp, char *str) {
return Parrot_new_string(interp,
str,
strlen(str),
# New Ticket Created by "Nikolay Ananiev"
# Please include the string: [perl #41125]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41125 >
Fixes the reallyinstall target on Win32
root.in.patch
Description: Binary data
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to
complete your request.
Please contact the server administrator, [EMAIL PROTECTED] and inform them of
the time the error occurred, and anything you might have done that may have
caused the error.
