Re: [CVS ci] Parrot_destroy

Brent Dax wrote: Leopold Toetsch: # - string_set() is gone, highly (WRT malloc) illegal reusage # of existing # string headers - and unnecessary IMHO I specifically asked for and received permission from Dan for this. It's designed to remove the need to pass in pointers-to-pointers-to-headers

Re: [perl #18191] [PATCH] t/src/manifest.t needs to skip 2 tests if no CVS.

Andy Dougherty (via RT) wrote: # New Ticket Created by Andy Dougherty # Please include the string: [perl #18191] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=18191 > Thanks, applied with Parrot_destroy changes, leo

RE: [CVS ci] Parrot_destroy

Leopold Toetsch: # - string_set() is gone, highly (WRT malloc) illegal reusage # of existing # string headers - and unnecessary IMHO I specifically asked for and received permission from Dan for this. It's designed to remove the need to pass in pointers-to-pointers-to-headers in functions with s

Re: Need for fingerprinting? [was: Re: What to do if Digest::MD5 is unavailable?]

Leo -- Here's one of the early fingerprinting patches, 2001-09-14: http://archive.develooper.com/perl6-internals@;perl.org/msg04063.html Here's where Simon removed Digest::MD5, 2001-09-18: http://archive.develooper.com/cvs-parrot@;perl.org/msg00151.html Here's one of the messages abou

Re: Need for fingerprinting? [was: Re: What to do if Digest::MD5 is unavailable?]

[EMAIL PROTECTED] wrote: All -- FWIW, this stuff came up early on in Parrot's infancy. Pointers, hints, information ... On a related note, I'm working on a toy VM outside of Parrot to demonstrate the technique I've proposed here in the past, Pointers, hints, information ... thanks, leo

[CVS ci] Parrot_destroy

Finally and after more changes I like to ci in one bunch, the parrot interpreter is (almost) memory leak free. Summary Currently broken test: - t/op/interp_2 with standard allocator and --gc-malloc Memory leakages: - PIO (PIO_new doesn't remember ParrotIO structures) - rx (bitmaps) - intstack (

Need for fingerprinting? [was: Re: What to do if Digest::MD5 is unavailable?]

All -- FWIW, this stuff came up early on in Parrot's infancy. At one time we had fingerprinting, then we removed it. At one time it was MD5, then we went away from MD5. IM(NS)HO, the better approach overall is to remove the need for fingerprinting altogether. I used to know roughly how to get f

[COMMIT] t/src/manifest.t

I added a local to $_ in t/src/manifest.t to avoid an undef warning in 5.005_03's File::Find Nicholas Clark -- Befunge better than perl? http://www.perl.org/advocacy/spoofathon/

Re: Questions about Px registers and memory usage [PATCH]

Peter Gibbs wrote: Clinton A. Pierce wrote: LOOP: new P1, .PerlHash branch LOOP This is simply a long-standing GC bug. Try the attached patch and see if it helps. Thanks for clarifying this. Actually, when introducing GC_IS_MALLOC I was bug compatible too ;-) Patch included in Parrot_

Re: cvs commit: parrot chartype.c datatypes.c disassemble.c dod.c encoding.c global (fwd)

Josh Wilmes wrote: FYI- I just re-indented a bunch of code, using the tools/dev/run_indent.pl script. I see really no need for quoting this stuff and plz next time wait, until real changes are committed - I did announce them. --Josh Thanks, leo

Re: Questions about Px registers and memory usage [PATCH]

Clinton A. Pierce wrote: > LOOP: new P1, .PerlHash > branch LOOP > What happens is that memory gets chewed up > quickly. Do I have the wrong idea of how the Px registers are used to point > to things (god, I hope not) or is there some GC that needs to happen that > isn't (and I can expect it t