The "foo:" part is the context. The "Unable to open file" part is the error
message. The "because it doesn't exist." part is the reason. This message has
- no suggestion. Where possible, the imlementation of lib/System should use
+ no suggestion. Where possible, the implementation of lib/System should use
operating system specific facilities for converting the error code returned by
a system call into an error message. This will help to make the error message
more familiar to users of that type of operating system.
None of the lib/System interface functions may be declared with C++
throw() specifications on them. This requirement makes sure that the
- compler does not insert addtional exception handling code into the interface
+ compiler does not insert additional exception handling code into the interface
functions. This is a performance consideration: lib/System functions are at
the bottom of the many call chains and as such can be frequently called. We
need them to be as efficient as possible.
@@ -374,7 +374,7 @@ Notes:
In order to provide different implementations of the lib/System interface
for different platforms, it is necessary for the library to "sense" which
operating system is being compiled for and conditionally compile only the
- applicabe parts of the library. While several operating system wrapper
+ applicable parts of the library. While several operating system wrapper
libraries (e.g. APR, ACE) choose to use #ifdef preprocessor statements in
combination with autoconf variable (HAVE_* family), lib/System chooses an
alternate strategy.
@@ -383,7 +383,7 @@ Notes:
functions for a particular operating system variant. The functions defined in
that file have no #ifdef's to disambiguate the platform since the file is only
compiled on one kind of platform. While this leads to the same function being
- imlemented differently in different files, it is our contention that this
+ implemented differently in different files, it is our contention that this
leads to better maintenance and easier portability.
For example, consider a function having different implementations on a
variety of platforms. Many wrapper libraries choose to deal with the different
@@ -407,7 +407,7 @@ Notes:
specific flavors and versions of the operating system. In that case you end up
with multiple levels of nested #if statements. This is what we mean by "#ifdef
hell".
-
To avoid the situation above, we've choosen to locate all functions for a
+
To avoid the situation above, we've chosen to locate all functions for a
given implementation file for a specific operating system into one place. This
has the following advantages:
diff --git a/docs/index.html b/docs/index.html
index cbd8cebf643..c90ab9a751d 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -171,7 +171,7 @@ generator.
on how to write a new alias analysis implementation or how to use existing
analyses.
-- The Stacker Cronicles - This document
+
- The Stacker Chronicles - This document
describes both the Stacker language and LLVM frontend, but also some details
about LLVM useful for those writing front-ends.