Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r1 (yet-another-logger-0.2.3.1-r1) |
2015-11-18T23:15:00Z |
larsk |
09206c65c7dfc32bff85a2f2f295561bfcb95067f74d460a0597ce448ed6fb27
|
|
Changed description
from A logging framework written with flexibility and performance
in mind.
= Quick Start
> import System.Logger
>
> main ∷ IO ()
> main = withConsoleLogger Info $ do
> logg Info "moin"
> withLabel ("function", "f") f
> logg Warn "tschüss"
> where
> f = withLevel Debug $ do
> logg Debug "debug f"
= Description
/This Version is yet a preview/
The logging system consists of four main parts:
1. The logging front-end are those types and functions that are used
to produce log messages in the code. This includes the 'LogLevel'
type, the 'LogPolicy' type, the 'LogLabel' and 'LogScope' types,
the 'LogFunction' type, and the 'MonadLog' type class.
2. The abstract 'LoggerCtx' is the context through which the 'LogFunction'
delivers log messages to the logger back-end.
3. The formatter is a function for serializing log messages.
4. The logger back-end is a callback that is invoked by 'Logger' on
each log messages. The logger back-end applies the formatting function
and delivers the log messages to some sink.
The framework allows to combine this components in a modular way. The
front-end types, the 'Logger', and the back-end callback are represented
by types or type classes. The formatter exists only as a concept
in the implementation of back-ends. These types and concepts together
form the abstract logger interface that is defined in the module
"System.Logger.Types".
The package also provides a concrete Logger that implements these components
in the module "System.Logger.Logger" and "System.Logger.Backend.Handle"
to A logging framework written with flexibility and performance
in mind.
= Quick Start
> import System.Logger
>
> main ∷ IO ()
> main = withConsoleLogger Info $ do
> logg Info "moin"
> withLabel ("function", "f") f
> logg Warn "tschüss"
> where
> f = withLevel Debug $ do
> logg Debug "debug f"
= Description
The logging system consists of four main parts:
1. The logging front-end are those types and functions that are used
to produce log messages in the code. This includes the 'LogLevel'
type, the 'LogPolicy' type, the 'LogLabel' and 'LogScope' types,
the 'LogFunction' type, and the 'MonadLog' type class.
2. The abstract 'LoggerCtx' is the context through which the 'LogFunction'
delivers log messages to the logger back-end.
3. The formatter is a function for serializing log messages.
4. The logger back-end is a callback that is invoked by 'Logger' on
each log messages. The logger back-end applies the formatting function
and delivers the log messages to some sink.
The framework allows to combine this components in a modular way. The
front-end types, the 'Logger', and the back-end callback are represented
by types or type classes. The formatter exists only as a concept
in the implementation of back-ends. These types and concepts together
form the abstract logger interface that is defined in the module
"System.Logger.Types".
The package also provides a concrete Logger that implements these components
in the module "System.Logger.Logger" and "System.Logger.Backend.Handle"
|
| -r0 (yet-another-logger-0.2.3.1-r0) |
2015-05-07T05:37:31Z |
larsk |
0936c4e0c4f8f686b522df2302d8c119631cd25a2d176ec8251750e3ad548646
|
|
|