This is not internal. I have one low level library which define a list of macro for doing assertion. (EXALT_ASSERT_*). These macros use EXALT_LOG_*. The daemon and the dbus library use these assertions, that's why EXALT_LOG is not internal.
2009/9/1 Gustavo Sverzut Barbieri <barbi...@profusion.mobi> > On Tue, Sep 1, 2009 at 7:14 PM, Atton Jonathan<jonathan.at...@gmail.com> > wrote: > > I suppose I can defines these 3 macros in the main library: > > > > #define EXALT_LOG_WARN(...) EINA_LOG_DOM_WARN(EXALT_LOG_DOMAIN, > __VA_ARGS__) > > #define EXALT_LOG_CRIT(...) EINA_LOG_DOM_CRIT(EXALT_LOG_DOMAIN, > __VA_ARGS__) > > #define EXALT_LOG_INFO(...) EINA_LOG_DOM_INFO(EXALT_LOG_DOMAIN, > __VA_ARGS__) > > I find the EXALT_LOG_ prefix useless as it's internal, but if you like > it, keep it (I see you committed like it already). > > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -------------------------------------- > MSN: barbi...@gmail.com > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 > -- Regards. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
