From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jason Sallis <jsallis@gmail.com>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: Re: looking for a recommendation for C logging library
Date: Fri, 3 Jun 2005 19:25:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0506031924020.16283@localhost.localdomain> (raw)
In-Reply-To: <73a776530506031320617c40ac@mail.gmail.com>
On Fri, 3 Jun 2005, Jason Sallis wrote:
> I've never personally tried it, but log4c
> (http://log4c.sourceforge.net/) might be worth checking out. I've
> worked with both log4j and log4net extensively and since this project
> is based on log4j, I would assume that it would meet your needs.
>
> j-sa
in fact, that's the very one i started looking at, having found it at
freshmeat. my only concern is that this is going to be part of an
embedded system so space will be an issue. as long as it isn't a
space hog, it's a possibility.
rday
prev parent reply other threads:[~2005-06-03 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 17:08 looking for a recommendation for C logging library Robert P. J. Day
2005-06-03 20:20 ` Jason Sallis
2005-06-03 23:25 ` Robert P. J. Day [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0506031924020.16283@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=jsallis@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).