On Friday, 16 September 2005, at 12:00:25 (-0700), E CVS List wrote: > Enlightenment CVS committal > > Author : dj2 > Project : e17 > Module : libs/ewl > > Dir : e17/libs/ewl/src/lib > > > Modified Files: > ewl_callback.c ewl_callback.h ewl_enums.h ewl_widget.c > ewl_widget.h > > > Log Message: > - convert the ewl_callbacks to use an array for their storage instead of an > ecore_list. The ecore_list is too heavyweight for what we need in the > callbacks.
<<snip 600+ line patch>> It's things like this that make me wish people would consider the LibAST object model. Changing between "list" implementations (array, linked list, doubly-linked list, and perhaps trees in the future) is a one-line code change and can even be done at runtime! And the additional overhead is minimal (a couple extra pointers per list). Has anyone even bothered to look at it? Is there something wrong with it? Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "When I was in prison, I was wrapped in all those deep books. That Tolstoy crap. People shouldn't read that stuff." -- boxer Mike Tyson on what he read before he decided he preferred comic books ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
