On Thu, Aug 11, 2016 at 11:23 AM, Gustavo Sverzut Barbieri <barbi...@gmail.com> wrote: > On Thu, Aug 11, 2016 at 2:21 AM, Carsten Haitzler <ras...@rasterman.com> > wrote: >> On Wed, 3 Aug 2016 01:29:39 -0300 Gustavo Sverzut Barbieri >> <barbi...@gmail.com> >> said:
[snip] >>> > i really don't like error as an int. really don't. a proper enum and/or >>> > struct with fields like enum for error type and maybe a string for error >>> > extra info (human readable from perror() style?) >>> >>> is Eina_Error ok? >> >> errr... thats horrible., it's a global TLS. ugh. :( make it an enum : > > Okay, so the new trend is to convert all possible errors to > context-specific errors? In the old days it was about eina_errors... > :-) > > will be kinda of a pain to map all possible errnos to enums, but i can > do it. (the other approach was to register all errnos at load time and > do a simple conversion as generic function eina_error_from_errno kinda > of thing). No. Please make it an Eina_Error! It is the only way to sensibly treat errors in bindings in a automatic-way. [snip] Regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
