Re: l_alloc called for free on NULL regularly

[Sean Conner <sean@...>]

It was thus said that the Great Francisco Olarte once stated:
> On Sat, 1 Apr 2023 at 14:04, Michael L. <michael.lix12@gmail.com> wrote:
> >
> > It does not really matter for the code in the end. I can I would
> > simply like to know this out of curiosity. These calls just seem
> > unnecessary to me. The lua documentation even says that free(NULL)
> > should has no effect, so why even call it?
> 
> Why not?

  Because the new C23 standard is looking to make realloc(x,0) **UNDEFINED
BEHAVIOR**!  [1] In fact, C17 apparently make realloc(x,0) as free() as
**OBSOLESCENT**!  (really big bold upper case etc. to drive the point
across).  Beware of using Lua with C23 it seems.

> It is not just lua, in C free(NULL) is no-op, realloc(x,0) is
> equivalent to free(x). This is useful to simplify error recoveries and
> function exits.

  For now.

  -spc

[1]	https://queue.acm.org/detail.cfm?id=3588242