Fix typos

This commit is contained in:
Sean Moon 2013-05-09 02:34:47 +09:00
parent 37becd887e
commit bd4ee7c7d2
27 changed files with 35 additions and 35 deletions

View file

@ -20,7 +20,7 @@
// calling the destructors on them.
// One subtle point that needs to be addressed is how to handle
// failures while running the user provided initializer function. It
// is important to not run the destructor on uninitalized objects, but
// is important to not run the destructor on uninitialized objects, but
// how to detect them is somewhat subtle. Since alloc() can be invoked
// recursively, it is not sufficient to simply exclude the most recent
// object. To solve this without requiring extra space, we use the low

View file

@ -15,7 +15,7 @@ or transformed to and from, byte vectors.
The `FlatPort` and `FlatChan` types implement the generic channel and
port interface for arbitrary types and transport strategies. It can
particularly be used to send and recieve serializable types over I/O
particularly be used to send and receive serializable types over I/O
streams.
`FlatPort` and `FlatChan` implement the same comm traits as pipe-based
@ -55,7 +55,7 @@ use core::sys::size_of;
use core::vec;
/**
A FlatPort, consisting of a `BytePort` that recieves byte vectors,
A FlatPort, consisting of a `BytePort` that receives byte vectors,
and an `Unflattener` that converts the bytes to a value.
Create using the constructors in the `serial` and `pod` modules.
@ -819,7 +819,7 @@ mod test {
}
}
// Reciever task
// Receiver task
do task::spawn || {
// Wait for a connection
let (conn, res_chan) = accept_port.recv();
@ -838,7 +838,7 @@ mod test {
for int::range(0, 10) |i| {
let j = port.recv();
debug!("receieved %?", j);
debug!("received %?", j);
assert!(i == j);
}

View file

@ -623,7 +623,7 @@ pub mod groups {
desc_sep
};
// Normalize desc to contain words seperated by one space character
// Normalize desc to contain words separated by one space character
let mut desc_normalized_whitespace = ~"";
for str::each_word(desc) |word| {
desc_normalized_whitespace.push_str(word);

View file

@ -420,7 +420,7 @@ mod test {
if result::is_err(&ga_result) {
fail!(~"got err result from net::ip::get_addr();")
}
// note really sure how to realiably test/assert
// note really sure how to reliably test/assert
// this.. mostly just wanting to see it work, atm.
let results = result::unwrap(ga_result);
debug!("test_get_addr: Number of results for %s: %?",

View file

@ -565,7 +565,7 @@ pub mod node {
*
* # Fields
*
* * byte_offset = The number of bytes skippen in `content`
* * byte_offset = The number of bytes skipped in `content`
* * byte_len - The number of bytes of `content` to use
* * char_len - The number of chars in the leaf.
* * content - Contents of the leaf.

View file

@ -32,7 +32,7 @@ pub mod rustrt {
}
// The name of a test. By convention this follows the rules for rust
// paths; i.e. it should be a series of identifiers seperated by double
// paths; i.e. it should be a series of identifiers separated by double
// colons. This way if some test runner wants to arrange the tests
// hierarchically it may.

View file

@ -222,6 +222,6 @@ mod test {
exit_po.recv();
};
debug!(~"test_stress_gl_uv_global_loop_high_level_global_timer"+
~" exiting sucessfully!");
~" exiting successfully!");
}
}

View file

@ -243,7 +243,7 @@ fn impl_uv_iotask_async(iotask: &IoTask) {
exit_po.recv();
}
// this fn documents the bear minimum neccesary to roll your own
// this fn documents the bear minimum necessary to roll your own
// high_level_loop
#[cfg(test)]
fn spawn_test_loop(exit_ch: ~Chan<()>) -> IoTask {

View file

@ -269,7 +269,7 @@ pub struct sockaddr_in {
}
// unix size: 28 .. FIXME #1645
// stuck with 32 becuse of rust padding structs?
// stuck with 32 because of rust padding structs?
#[cfg(target_arch="x86_64")]
pub struct sockaddr_in6 {
a0: *u8, a1: *u8,
@ -286,7 +286,7 @@ pub struct sockaddr_in6 {
}
// unix size: 28 .. FIXME #1645
// stuck with 32 becuse of rust padding structs?
// stuck with 32 because of rust padding structs?
pub type addr_in = addr_in_impl::addr_in;
#[cfg(unix)]
pub mod addr_in_impl {
@ -1376,7 +1376,7 @@ mod test {
let tcp_init_result = tcp_init(test_loop as *libc::c_void,
tcp_handle_ptr);
if (tcp_init_result == 0) {
debug!(~"sucessful tcp_init_result");
debug!(~"successful tcp_init_result");
debug!(~"building addr...");
let addr = ip4_addr(ip, port);