[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Are there some potential problems if I use a self-defined memory acquirement function instead of realloc(3) in the l_alloc function?
- From: Stefan <ste@...>
- Date: Mon, 10 Aug 2020 17:33:00 +0200
Am 10.08.2020 um 16:34 schrieb Roberto Ierusalimschy:
>> I think Lua relies on the behaviour that the realloc-like function
>> does not return a different pointer (copy) for shrinking an existing
>> block. Maybe that could be a problem for some allocators.
> Lua does not rely on that. The only assumption was that shrinking
> an existing block could not fail, but it can move the block without
> problems. Actually, the test suite in Lua has a mode that forces every
> single reallocation (growing, shrinking, or to the same size!) to move
> the block.
My test program was flawed. Sorry.
> Lua 5.4 has removed this restriction of "no fail when shrinking".
> -- Roberto
Wow, so this is why it is no longer in the manual.
I wonder if there is any system with C support left that can't
run Lua :)