On Wednesday 02 May 2007 19:33:18 James Keenan via RT wrote:
> I use Subversion as my local version control client, so I'm not currently
> able to write tests for the svk-associated stanza. Hence, testing coverage
> is lower than I would normally be satisfied with. Patches from svk users
> would
See attached patch revision.patch.txt. Per discussion on list with particle,
lib/Parrot/
Revision.pm is revised to eliminate unassignable variable $svn_entries and one
stanza of
code associated therewith. Also eliminates unused variable $ent. I also add 4
test files: two
in t/configure/ an
Patch applied in r18405.
Hack described in Configure.pl and found in Parrot::Configure::Step is fixed
by making Parrot::Configure object into a singleton. This entailed changes in
those two packages as well as config/init/defaults.pm.
Also: Parrot::Configure::Data::slurp() now checks Parrot::Co
I'm working on ticket #38929
( http://rt.perl.org/rt3//Public/Bug/Display.html?id=38929 )
As far as I can tell, there's a JIT_EMIT #define that the .c files set
before they #include jit_emit.h, and what it does is switch out parts of
jit_emit.h.
What is this good for?
(This is important for me
# New Ticket Created by "Yehoshua Sapir"
# Please include the string: [perl #42861]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42861 >
This has a lot to do with tickets #42558 and #34994:
(there's quite a bit to read in
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #42865]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42865 >
There's no real way to set a vtable function at runtime. It's
possible to use the PI
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #42864]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42864 >
Copying a subroutine/method that has also been marked as a :vtable
function also cop
On Tue, 1 May 2007, James Keenan via RT wrote:
> On Tue Apr 10 01:45:31 2007, [EMAIL PROTECTED] wrote:
> > Configure should act as though writing --foo=no is false instead of
> > true. Tonight I tried using --execcapable=no to get around a compile
> > failure, but then realized that it would pr
At the time I got this email, it was still failing when I applied the
patch, but with r18394 it's currently working again without problems.
A full make test passes with only previously failing errors.
On May 1, 2007, at 2:11 PM, chromatic wrote:
On Sunday 29 April 2007 11:18:20 Joshua Isom w
