From: Tom H. <tom...@pa...> - 2010-10-05 09:35:34
|
On Tue, 2010-10-05 at 11:29 +0200, Vincent Torri wrote: > because it's useless ? That kind of stuff must be documented. If not, the > doc must be fixed. Hence, internal or not, a user knows what the > initialisation does. Useless: yes, costly: no, future-proof: more than without. What do you need to doc? everything you init? And let's say you do doc that you init eina, so the user of ecore_init sees that and doesn't init eina himself, all is good, until ecore_init stops initing eina and that application will break. Eina is an extreme example because it's unlikely to be dropped, but what about glib? glib was probably used before eina, and then one day it got dropped. It's the same idea, in different flavor. As I said, it doesn't really matter this time (because ffs it's eina), but I think explicitly stating what you need (in the code) is nicer and more obvious. -- Tom. |