Hi, As it seems like a good time to break the EFL agains :-). I would like to discuss API/ABI break of eet. I am currently working on adding crypto to eet. My current code only require a key and generate the needed salt and IV for the encryption. So I need to add one more parameter (the key) to all read and write operation of eet. I have currently two possibilities, double the number of function, or just change the existing one. Of course the later solution sounds a little bit cleaner, but it will break all eet applications.
A quick search of eet_open in the svn give me 43 differents file using it. Sounds like not a big deal to break it. This could be also be a good time to cleanup the parameters of eet_data_descriptor_element_add also. So guys, what do you think of this move ? -- Cedric BAIL ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
