Re: [Flex-devel] Allocation functions

[Will E. <wes...@gm...>]

Ah, yeah, I am guessing this is old stuff that used to be necessary.

so yes, those functions can come out.

On Monday,  7 December 2015,  8:31 pm -0500, Michael McConville <mm...@my...> wrote:

> 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.
> 
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Flex-devel mailing list
> Fle...@li...
> https://lists.sourceforge.net/lists/listinfo/flex-devel

-- 
Will Estes
wes...@gm...