2014-12-13 21:49:39 +00:00
|
|
|
log
|
|
|
|
===
|
|
|
|
|
2015-01-25 06:44:46 +00:00
|
|
|
A Rust library providing a lightweight logging *facade*.
|
2014-12-13 21:49:39 +00:00
|
|
|
|
|
|
|
[![Build Status](https://travis-ci.org/rust-lang/log.svg?branch=master)](https://travis-ci.org/rust-lang/log)
|
2015-04-29 17:41:25 +00:00
|
|
|
[![Build status](https://ci.appveyor.com/api/projects/status/nopdjmmjt45xcrki?svg=true)](https://ci.appveyor.com/project/alexcrichton/log)
|
2014-12-13 21:49:39 +00:00
|
|
|
|
2015-01-27 15:30:34 +00:00
|
|
|
* [`log` documentation](http://doc.rust-lang.org/log)
|
|
|
|
* [`env_logger` documentation](http://doc.rust-lang.org/log/env_logger)
|
2014-12-13 21:49:39 +00:00
|
|
|
|
2015-01-25 06:44:46 +00:00
|
|
|
A logging facade provides a single logging API that abstracts over the actual
|
|
|
|
logging implementation. Libraries can use the logging API provided by this
|
|
|
|
crate, and the consumer of those libraries can choose the logging
|
|
|
|
implementation that is most suitable for its use case.
|
|
|
|
|
2014-12-13 21:49:39 +00:00
|
|
|
## Usage
|
|
|
|
|
2015-01-27 07:56:55 +00:00
|
|
|
## In libraries
|
|
|
|
|
|
|
|
Libraries should link only to the `log` crate, and use the provided macros to
|
|
|
|
log whatever information will be useful to downstream consumers:
|
2014-12-13 21:49:39 +00:00
|
|
|
|
|
|
|
```toml
|
|
|
|
[dependencies]
|
2015-03-28 14:20:31 +00:00
|
|
|
log = "0.3"
|
2014-12-13 21:49:39 +00:00
|
|
|
```
|
|
|
|
|
2015-01-27 07:56:55 +00:00
|
|
|
```rust
|
|
|
|
#[macro_use]
|
|
|
|
extern crate log;
|
|
|
|
|
|
|
|
pub fn shave_the_yak(yak: &Yak) {
|
|
|
|
trace!("Commencing yak shaving");
|
|
|
|
|
|
|
|
loop {
|
|
|
|
match find_a_razor() {
|
|
|
|
Ok(razor) => {
|
|
|
|
info!("Razor located: {}", razor);
|
|
|
|
yak.shave(razor);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
Err(err) => {
|
|
|
|
warn!("Unable to locate a razor: {}, retrying", err);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
## In executables
|
|
|
|
|
|
|
|
Executables should chose a logger implementation and initialize it early in the
|
|
|
|
runtime of the program. Logger implementations will typically include a
|
|
|
|
function to do this. Any log messages generated before the logger is
|
|
|
|
initialized will be ignored.
|
|
|
|
|
|
|
|
The executable itself may use the `log` crate to log as well.
|
|
|
|
|
|
|
|
The `env_logger` crate provides a logger implementation that mirrors the
|
|
|
|
functionality of the old revision of the `log` crate.
|
|
|
|
|
|
|
|
```toml
|
|
|
|
[dependencies]
|
2015-03-28 14:20:31 +00:00
|
|
|
log = "0.3"
|
|
|
|
env_logger = "0.3"
|
2015-01-27 07:56:55 +00:00
|
|
|
```
|
2014-12-13 21:49:39 +00:00
|
|
|
|
|
|
|
```rust
|
2015-01-25 06:44:46 +00:00
|
|
|
#[macro_use]
|
2014-12-13 21:49:39 +00:00
|
|
|
extern crate log;
|
2015-01-27 07:56:55 +00:00
|
|
|
extern crate env_logger;
|
|
|
|
|
|
|
|
fn main() {
|
|
|
|
env_logger::init().unwrap();
|
|
|
|
|
|
|
|
info!("starting up");
|
|
|
|
|
|
|
|
// ...
|
|
|
|
}
|
2014-12-13 21:49:39 +00:00
|
|
|
```
|