On 3/1/07, Tilman Sauerbeck <[EMAIL PROTECTED]> wrote: > > ACK. I believe raster's reasoning for using lists in various spots that > would intuitively like to be hashes was the size of the entries that are > stored. IIRC evas/ecore_evas also use lists to store key/value userdata.
Is there extra storage overhead in the eet files for storing hash entries beyond storing the key/value pairs of a list? I haven't looked at this closely yet, but I will before making any further changes. The way I currently have it implemented is not a terrible trade-off if it saves space in the files. As rephorm pointed out, this will be a small runtime impact of approximately 1-2kb per edje file. The edje file's are cached so multiple references to an edje file will refer to the same hash table. And because of how evas hash tables work (NULL pointer for empty hash tables), it would only allocate the hash if there are data entries present. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
