.TH "todo" 3 "Mon May 2 2011" "Version 1.2.1" "log4c" \" -*- nroff -*-
.ad l
.nh
.SH NAME
todo \- Todo List 
 
.IP "\fBFile \fBappender.h\fP \fP" 1c
the appender interface needs a better configuration system depending on the layout type. The udata field is a just a trick. 
.PP
.PP
 
.IP "\fBFile \fBlayout.h\fP \fP" 1c
the layout interface needs a better configuration system depending on the layout type. The udata field is a just a trick.
.PP
a pattern layout would be welcomed !! 
.PP
.PP
 
.IP "\fBGlobal \fBlog4c_category_get_chainedpriority\fP(const log4c_category_t *a_category) \fP" 1c
the log4c_category_t is designed so that this method executes as quickly as possible. It could even be faster if the set priority was propagated through the children hierarchy of a category. 
.PP
.PP
 
.IP "\fBGlobal \fBlog4c_category_set_appender\fP(log4c_category_t *a_category, struct __log4c_appender *a_appender) \fP" 1c
need multiple appenders per category 
.PP
.PP
 
.IP "\fBClass \fBlog4c_location_info_t\fP \fP" 1c
this is not used 
.PP
.PP
 
.IP "\fBGlobal \fBlog4c_logging_event_new\fP(const char *a_category, int a_priority, const char *a_message) \fP" 1c
need to handle multi-threading (NDC) 
.PP