Re: sv_grow() and malloc()

Dave Mitchell wrote:
> So in conclusion, I am proposing for discussion right now,
> a) re-enabling malloc_size() where available, and
>    probing at runtime startup to determine constants A and B where mallocs
>    will be of the form A+nB;
> b) adjusting the SvCUR verses SvLEN algorithm as suggested above.
>    I'm not totally wedded to my exact suggested criteria 2 paragraphs
>    above; I'm open to suggestions.

I agree with both.

• sv_grow() and malloc() by Dave Mitchell
• Re: sv_grow() and malloc() by demerphq
• Re: sv_grow() and malloc() by Dave Mitchell
• Re: sv_grow() and malloc() by Father Chrysostomos
• Re: sv_grow() and malloc() by Aaron Crane
• Re: sv_grow() and malloc() by H.Merijn Brand
• Re: sv_grow() and malloc() by Tony Cook
• Re: sv_grow() and malloc() by Dave Mitchell
• Re: sv_grow() and malloc() by Steve Hay
• Re: sv_grow() and malloc() by Andy Dougherty
• Re: sv_grow() and malloc() by Craig A. Berry
• Re: sv_grow() and malloc() by Andy Dougherty
• Re: sv_grow() and malloc() by Aaron Crane
• Re: sv_grow() and malloc() by Father Chrysostomos
• Re: sv_grow() and malloc() by Dave Mitchell