Brett Nash wrote: > ............ > Until then, I'm going to continue to put people checking the alloca > return value in the category of "doesn't know what alloca does, and > unable to read documentation". > > People can make oversights now and then, even change their code from a malloc to an alloca and forget they've done so, etc. How can you be so certain why they're checking for the return value.
In any case, you may want to bring this discussion up with the author of: evas/src/lib/engines/common/evas_map_image_internal.c where around line 78 you'll find some code that reads: // // allocate some spans to hold out span list spans = alloca((yend - ystart + 1) * sizeof(Line)); if (!spans) return; ____________________________________________________________ Get Free Email with Video Mail & Video Chat! http://www.juno.com/freeemail?refcd=JUTAGOUT1FREM0210 ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
