linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Sallis <jsallis@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.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 14:20:13 -0600	[thread overview]
Message-ID: <73a776530506031320617c40ac@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506031306450.29227@localhost.localdomain>

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

On 6/3/05, Robert P. J. Day <rpjday@mindspring.com> wrote:
> 
>  in some code i inherited, i'm tempted to replace the current,
> cumbersome, in-house collection of logging code with a public package
> of some kind.  any recommendations for a decent C logging library?
> it should support selectable output files, multiple warning levels,
> all the usual stuff.
> 
>  thoughts?
> 
> rday
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2005-06-03 20:20 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 [this message]
2005-06-03 23:25   ` Robert P. J. Day

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=73a776530506031320617c40ac@mail.gmail.com \
    --to=jsallis@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /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).