2012/3/27 Vikram Narayanan <vikram...@gmail.com>: > On 3/27/2012 12:37 AM, Michael Blumenkrantz wrote: >> On Tue, 27 Mar 2012 00:21:19 +0530 >> Vikram Narayanan<vikram...@gmail.com> wrote: >> >>> In ecrire, >>> Check return values of *alloc functions, though its unlikely to >>> fail. There are chances though! >>> >>> Comments please. >>> >>> Thanks, >>> Vikram >> >> efl applications typically don't bother checking return values on these >> functions because you're fucked no matter what if they fail > > I don't understand your language. > Even if its not necessary, it's a good programming practice to do it > atleast for memory allocation functions.
Yeah, It's good practice to check return value of functions. But malloc() is optimized in linux. So it is not guaranteed to return non-NULL even though it's availabe. And discomfitor said that EFL typically do not check it. I thinks that it is because malloc() fail, whole things fail. > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- BRs, Kim. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
