| commit | 49f5882a72fd57c50ad41cf1ea2f847b2e76d288 | [log] [tgz] |
|---|---|---|
| author | Brian Campbell <lambda@continuation.org> | Thu Mar 24 16:43:53 2016 -0400 |
| committer | Brian Campbell <lambda@continuation.org> | Thu Mar 24 18:45:22 2016 -0400 |
| tree | f891915da3805dfecaf910b78951d0bd5a0d2e6d | |
| parent | 86b8253fb2ea3382e3b4ab2fedade12737415c0b [diff] |
Add NetworkEndian alias Network byte order is defined by [RFC 1700][1] to be big-endian, and is referred to in several protocol specifications. This type is an alias of BigEndian. This alias can be used to make it more clear why you're using a particular byte order in code, if you are implementing a specification that refers to network byte order. [1]: https://tools.ietf.org/html/rfc1700
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.4"
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());