I'm in the middle of a rather large project, and stopped to do a memory
usage sanity check. To my surprise I found a leak and traced it back to
the way I was allocating PerlHashes and whatnot.
To boil it down further, look at this PASM:
LOOP: new P1, .PerlHash
branch LOOP
What I'd *expect
Jonathan Sillito (via RT) <[EMAIL PROTECTED]> writes:
[...]
> The attached patch implements a very complete set of lexical scope
> semantics. For those that have been following along, here are some
> highlights.
>
> - supports (fast) access by lexical position, rather than just by name
>
> - add
FYI- I just re-indented a bunch of code, using the tools/dev/run_indent.pl
script.
--Josh
--- Forwarded Message
Date:02 Nov 2002 14:57:48 +
From:[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: cvs commit: parrot chartype.c datatypes.c disassemble.c dod.c encoding
On Sat, Nov 02, 2002 at 05:46:07AM -, [EMAIL PROTECTED] wrote:
> cvsuser 02/11/01 21:46:07
>
> Modified:include/parrot datatypes.h
> Log:
> Fixed errors flagged by "make check_source"
Is it sensible to arrange for CVS to refuse to commit C files unless they
pass the source check
Leopold Toetsch (via RT) wrote:
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #18142]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18142 >
I have Parrot_destroy + related changes almost read
