Re: Avoiding the deadlands

At 4:54 AM -0400 4/9/02, Michel J Lambert wrote: > > So, I think #2 is the way to go. We'll add a new flag, >> (BUFFER|PMC)_stay_of_execution_FLAG or something, that gets added to >> allocated PMCs and Buffers. It'll be treated the same way as the >> constant/immortal flag is treated for DOD p

Patches, patches, patches...

To forestall potential incidents of Warnock's Dillemma... I'm about to apply a whole heap 'o patches to Parrot. (With appropriate [APPLIED] responses, I hope) If, at the end of the day, I have *not* applied or commented on a patch you've sent, it means I've Officially Missed It, so give anothe

Re: PMC confusion

At 12:47 AM -0500 4/2/02, Will Coleda wrote: >I can't concat strings to a PerlString, I have to assign the constant >string to another PerlString to do the concat... > >Is this just that a suitable entry in perlstring.pmc needs to be >created? Yep. -- Dan

Re: [PATCH] Parrot_(re)allocate_buffer

At 6:52 PM -0500 4/3/02, Bryan C. Warnock wrote: >On Wednesday 03 April 2002 16:55, Michel J Lambert wrote: >> > Why add new functions instead of patching the current ones? >> >> I didn't know if the original functions still had a purpose. Perhaps you >> would want to Parrot_allocate for someth

Re: Patches, patches, patches...

At 12:40 PM 4/10/2002 -0400, Dan Sugalski wrote: >To forestall potential incidents of Warnock's Dillemma... > >I'm about to apply a whole heap 'o patches to Parrot. (With appropriate >[APPLIED] responses, I hope) If, at the end of the day, I have *not* >applied or commented on a patch you've sen

Re: Patches, patches, patches...

At 12:53 PM -0400 4/10/02, Melvin Smith wrote: >At 12:40 PM 4/10/2002 -0400, Dan Sugalski wrote: >>To forestall potential incidents of Warnock's Dillemma... >> >>I'm about to apply a whole heap 'o patches to Parrot. (With >>appropriate [APPLIED] responses, I hope) If, at the end of the day, >>I

Memory allocation changes

Okay, having seen the discussion and now realized that my initial cut was too rough, here are some changes: Parrot_allocate now takes a Buffer pointer and allocates into it, setting the length to what was really allocated. Parrot_reallocate takes a Buffer pointer and a size, and resizes things

[PATCH] PerlString fixes (and tests)

The enclosed patch makes a number of changes to perlstring.pmc, to bring it in line with my understanding of how PMCs are supposed to work. Specifically, unless we _know_ the type of the source and destination PMCs, we should always access them through their get_... and set_... methods. In

Non-anchored GC memory?

Can anyone think of a good enough reason to allow unanchored GCable memory? I can see it being useful for really temporary allocations that later get dropped, but that seems horribly error-prone, and I'm not sure I want to set us up for tracking down that sort of thing for the rest of eternity

Re: Worst-case GC Behavior?

At 9:39 AM +0200 4/9/02, Peter Gibbs wrote: >One option might be a >threshold - if, after the DOD run, there is still less than N headers >available, allocate more even though we can satisfy the immediate >requirement. This would improve performance by reducing the number of DOD >runs, but at the

Re: Worst-case GC Behavior?

> >One option might be a > >threshold - if, after the DOD run, there is still less than N headers > >available, allocate more even though we can satisfy the immediate > >requirement. This would improve performance by reducing the number of DOD > >runs, but at the cost of additional memory - a clas

Re: Worst-case GC Behavior?

At 4:38 PM -0400 4/10/02, Michel J Lambert wrote: > > >One option might be a >> >threshold - if, after the DOD run, there is still less than N headers >> >available, allocate more even though we can satisfy the immediate >> >requirement. This would improve performance by reducing the number of

Re: Non-anchored GC memory?

On Wed, Apr 10, 2002 at 03:52:09PM -0400, Dan Sugalski wrote: > Can anyone think of a good enough reason to allow unanchored GCable > memory? I can see it being useful for really temporary allocations > that later get dropped, but that seems horribly error-prone, and I'm > not sure I want to se

I submit for your aproval . . .

Hey guys: Here is what I have so far of the string_nprintf function. As of now it only handles C string backslash escape sequences and regular chars from the format string. My primary concern is whether I am using BUFFER_immobile_FLAG the correct way to protect myself from GC. I also dont kn

Re: I submit for your aproval . . .

At 6:29 PM -0400 4/10/02, Roman Hunt wrote: >Hey guys: > Here is what I have so far of the string_nprintf function. As of now it > only handles C string backslash escape sequences and regular chars >from the format string. My primary concern is whether I am using >BUFFER_immobile_FLAG the cor

Re: I submit for your aproval . . .

In message Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 6:29 PM -0400 4/10/02, Roman Hunt wrote: > > >also I think > >encoding_lookup() should accept an argument of "native". > > Good point, they should. OTOH, that makes some of this interestin

Re: Patches, patches, patches...

On Wednesday 10 April 2002 12:53 pm, Melvin Smith wrote: > I think there is at least one outstanding patch from Brian Warnock called: > "stacks.c" Hmmm, looking in my outbox, I see only one recent patch of mine that mentions stacks.c, and its been applied. (Although I don't know when. It could

Re: Patches, patches, patches...

At 10:40 PM 4/10/2002 -0400, Bryan C. Warnock wrote: >On Wednesday 10 April 2002 12:53 pm, Melvin Smith wrote: > > I think there is at least one outstanding patch from Brian Warnock called: > > "stacks.c" > >Hmmm, looking in my outbox, I see only one recent patch of mine >that mentions stacks.c, a

What I'm working on before I go offline for 2 weeks

I'm getting married Saturday and going on honeymoon for 10 days. So I'll just update you guys on what I'm working on just in case I fall of the face of the earth for the next 2 weeks, I have a lot of unflushed stuff. Parrot: 1) Porting to WinCE for PocketPC The first cut will be posted as