Commit graph

4 commits

Author SHA1 Message Date
obache
16cb29aa83 Update p5-Log-Agent to 0.307.
Patch provided by Martin Wilke via PR 34347.

Changes:
Sun Oct  2 12:57:35 EDT 2005   Mark Rogaski <mrogaski@cpan.org>

. Description:	0.3.7

        Replaced a non-localized modification $^W with "no warnings" so
        warnings are no disabled globally.  Thanks to Andreas Vierengel for
        pointing this out.

        Fixed formatting behavior for strings that contain "%%" without any
        other formating characters.  Thanks to David Coppit for this one.

        Fixed a minor undef warning in a major kludge in the Agent::Driver
        code.
2006-10-28 11:48:31 +00:00
wiz
76a1a71d47 Update to 0.306, from PR 29852:
Changes from 0.3.3:

Mon Feb  2 22:34:28 EST 2004   Mark Rogaski

. Description:  0.3.6

        Stripped line endings in common tests to allow tests to succeed
        under non-UN*X environments.  Also replaced an unnecessary handle
        alias with the actual file name in t/file.t.  Thanks to Jay Lawrence
        and Terrence Brannon for pointing out the test problems.

Sat Sep 27 13:56:58 EDT 2003   Mark Rogaski

. Description:  0.3.5

        Added a wrapper for &AutoLoader::AUTOLOAD to save the value
        of $!, which is often clobbered before the substitution of
        "%m" by logxxx().

        Added a META.yml file and disabled autogeneration in Makefile.PL.

Sat Mar  8 11:43:41 EST 2003   Mark Rogaski

. Description:  0.3.4

        Made the logxxx() calls transparent to all (current)
        sprintf() formatting patterns.  Not all formatting
        errors will be caught before passed to sprintf(), but
        the obviously malformed ones will be detected.

        Added support for embedded newlines in messages passed to
        logcarp() and logxcarp().

Package change: add HOMEPAGE.
2005-04-04 09:31:03 +00:00
agc
4a3d2f7ce2 Add RMD160 digests. 2005-02-23 22:24:08 +00:00
mjl
a29ac9de3b Add p5-Log-Agent 0.303
Log::Agent is a general logging framework aimed at reusable modules.

Instead of having modules insist on using their onw logging reporting
(by hardwiring calls to warn() or syslog()) which can conflict with
the final application's choice, one may use logwarn() for instance to
emit a warning.
2003-02-11 23:29:56 +00:00