author | Michael Krelin <hacker@klever.net> | 2005-04-02 17:08:40 (UTC) |
---|---|---|
committer | Michael Krelin <hacker@klever.net> | 2005-04-02 17:08:40 (UTC) |
commit | 1a234a03b327b20bf7490c696ebc41a9d65117ac (patch) (unidiff) | |
tree | 8a62fb61dcb8abc7b9dab3bae68d7f4088224435 | |
parent | 8e7ab6661815e333ee9377c2655a03aee89372c2 (diff) | |
download | sitecing-1a234a03b327b20bf7490c696ebc41a9d65117ac.zip sitecing-1a234a03b327b20bf7490c696ebc41a9d65117ac.tar.gz sitecing-1a234a03b327b20bf7490c696ebc41a9d65117ac.tar.bz2 |
typo corrected
-rw-r--r-- | htdocs/exceptions/index.chtml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/htdocs/exceptions/index.chtml b/htdocs/exceptions/index.chtml index e66620a..6bb2a3c 100644 --- a/htdocs/exceptions/index.chtml +++ b/htdocs/exceptions/index.chtml | |||
@@ -8,17 +8,17 @@ | |||
8 | return "exceptions handling"; | 8 | return "exceptions handling"; |
9 | </%codemethod> | 9 | </%codemethod> |
10 | <%method void content() %> | 10 | <%method void content() %> |
11 | <h1>site-C-ing exception handling</h1> | 11 | <h1>site-C-ing exception handling</h1> |
12 | <p> | 12 | <p> |
13 | The purpose of this section is to give an overview of the <em>site-C-ing</em> | 13 | The purpose of this section is to give an overview of the <em>site-C-ing</em> |
14 | exception handling mechanism. Before the web visitor can see the page each | 14 | exception handling mechanism. Before the web visitor can see the page each |
15 | site-C-ing component goes through a few stages, namely, preprocessing, | 15 | site-C-ing component goes through a few stages, namely, preprocessing, |
16 | compiling and execution. Having three stages to go through also means the | 16 | compiling and execution. Having three stages to go through also means three |
17 | stages one can fail to go through and three exciting opportunities to handle | 17 | stages one can fail to go through and three exciting opportunities to handle |
18 | different errors. | 18 | different errors. |
19 | </p> | 19 | </p> |
20 | <p> | 20 | <p> |
21 | First each component is preprocessed so that you can feed the valid c++ code | 21 | First each component is preprocessed so that you can feed the valid c++ code |
22 | to the compiler. Here is where the preprocessor can choke at your broken | 22 | to the compiler. Here is where the preprocessor can choke at your broken |
23 | source code. Once preprocessor failes to parse your code it will throw an | 23 | source code. Once preprocessor failes to parse your code it will throw an |
24 | exception which <em>site-C-ing</em> will catch and pass to <a | 24 | exception which <em>site-C-ing</em> will catch and pass to <a |