On Tue, Apr 26, 2011 at 10:23 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Tue, 26 Apr 2011 14:24:19 +0200 Jérémy Zurcher <jer...@asynk.ch> said: > > though we value your patch and we always say "send patches"... we can't accept > that patch as it breaks api. we basically cannot break our api now we are 1.0 > - > not until a 2.0 and we're not jumping right on that any time soon. it's > evolution for now, not revolution :)
It's useless to expose such details, as we don't even write C code that uses it. Just bind ecore_evas and you'll be fine. Moreover, bindings should try to integrate nicely with environment, not blindly write code. For example, never expose eina_list, use Ruby's builtin list instead. Same for hash, stringshares and all. Jérémy even mentioned Ecore_Getopt, which is a bad example given that most high level languages have such thing nicely exposed... at least it is the case with Python (that I used optparse as base to create Ecore_Getopt). -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
