commit | 75d33fe4a804aca21d52ea6fa93374eaf0a67be3 | [log] [tgz] |
---|---|---|
author | Andrew Gallant <jamslam@gmail.com> | Sat Nov 07 18:22:53 2015 -0500 |
committer | Andrew Gallant <jamslam@gmail.com> | Sat Nov 07 18:22:53 2015 -0500 |
tree | 7196e21ebb06b3b5c7c67d12ec8fbbd8d462e3c1 | |
parent | 58bcaa8149c04430da33dd7a0fc945704774368d [diff] |
Add write_{int,uint}. Since this adds a new required method on the `ByteOrder` trait, this is a breaking change. This should only break crates that have custom implementations of the `ByteOrder` trait. To fix it, add an implementation for `write_uint`. [breaking-change]
This crate provides convenience methods for encoding and decoding numbers in either big-endian or little-endian order. This is meant to replace the old methods defined on the standard library Reader
and Writer
traits.
Dual-licensed under MIT or the UNLICENSE.
http://burntsushi.net/rustdoc/byteorder/.
The documentation includes examples.
This crate works with Cargo and is on crates.io. The package is regularly updated. Add it to your Cargo.toml
like so:
[dependencies] byteorder = "0.3"
If you want to augment existing Read
and Write
traits, then import the extension methods like so:
extern crate byteorder; use byteorder::{ReadBytesExt, WriteBytesExt, BigEndian, LittleEndian};
For example:
use std::io::Cursor; use byteorder::{BigEndian, ReadBytesExt}; let mut rdr = Cursor::new(vec![2, 5, 3, 0]); // Note that we use type parameters to indicate which kind of byte order // we want! assert_eq!(517, rdr.read_u16::<BigEndian>().unwrap()); assert_eq!(768, rdr.read_u16::<BigEndian>().unwrap());