I agree completely. but this does not only apply to del() functions, it will crash for ANY function being passed NULL. this is very bad.
On Fri, Dec 21, 2012 at 9:58 AM, Cedric BAIL <[email protected]> wrote: > On Fri, Dec 21, 2012 at 6:54 PM, Michael Blumenkrantz > <[email protected]> wrote: > > it seems that since the eo integration, functions such as > ecore_timer_del() > > which used to be harmless when called with NULL (possibly throwing an > error > > message) will now throw a CRI and probably abort(). this is definitely > not > > a good change, and imo a crash should never be the result of passing > > NULL...that was the whole point of safety macros > > I have been advocating for months that eo should del NULL object > without complains like free(NULL) does. It simplify and clarify the > calling code a lot... > -- > Cedric BAIL > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
