Re: [Flex-devel] Allocation functions

[Michael M. <mm...@my...>]

Will Estes wrote:
> Michael McConville wrote:
> > Is there any reason for the allocation functions like flex_alloc()
> > to stay around?
> 
> Context, please?
> 
> Probably not, and I'm all for making the flex codebase more readable,
> but what, specifically, do you have in mind? (Keeping in mind that I
> haven't read your latest pr yet.)

flex_alloc, flex_free, and flex_realloc are just aliases for stdlib
functions.* Unless there's a good reason for this, I think it'd be best
to just replace them with the corresponding stdlib functions.

* flex_free includes a NULL-check, but this is unnecessary. POSIX 
  specifies that free() be NULL-safe and all modern platforms comply.