log4c Reviews

User Ratings

3.0 out of 5 stars

★★★★★

★★★★

★★★

★★

★

ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

Rate This Project

Featured Reviews

Highest Rated

FYI: there is a bug in appender_type_rollingfile.c. fprintf causes this code to fail and take down all dependent apps. replacing with fputs fixes the bug. 168c168,169 < rc = fprintf(rfup->rfu_current_fp, a_event->evt_rendered_msg); --- > rc = fputs(a_event->evt_rendered_msg, rfup->rfu_current_fp);

Lowest Rated

Hello guys, as log4c stop its develop. I found many problems in log4c(memory leaking, low speed, bad model copied from log4j), so I write a new and better c log library -- zlog! https://github.com/HardySimpson/zlog you can have a try~~~

User Reviews

Filter Reviews:

All

ilyah1158 Posted 2012-04-17

FYI: there is a bug in appender_type_rollingfile.c. fprintf causes this code to fail and take down all dependent apps. replacing with fputs fixes the bug. 168c168,169 < rc = fprintf(rfup->rfu_current_fp, a_event->evt_rendered_msg); --- > rc = fputs(a_event->evt_rendered_msg, rfup->rfu_current_fp);
hardysimpson Posted 2012-03-26

Hello guys, as log4c stop its develop. I found many problems in log4c(memory leaking, low speed, bad model copied from log4j), so I write a new and better c log library -- zlog! https://github.com/HardySimpson/zlog you can have a try~~~

Previous
You're on page 1
Next