-rw-r--r-- | htdocs/exceptions/index.chtml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/htdocs/exceptions/index.chtml b/htdocs/exceptions/index.chtml index cc0ed8a..e66620a 100644 --- a/htdocs/exceptions/index.chtml +++ b/htdocs/exceptions/index.chtml | |||
@@ -1,26 +1,30 @@ | |||
1 | % html(); return; /* vim:set ft=sitecing: */ | 1 | % html(); return; /* vim:set ft=sitecing: */ |
2 | %%derive layout = "/ancestry/layout.chtml"; | 2 | %%derive layout = "/ancestry/layout.chtml"; |
3 | <%constructor> | ||
4 | PN_PREV("/simple","simple page","building a really simple page"); | ||
5 | PN_NEXT("/exceptions/preprocess","preprocess","preprocessing errors"); | ||
6 | </%constructor> | ||
3 | <%codemethod string title() %> | 7 | <%codemethod string title() %> |
4 | return "exceptions handling"; | 8 | return "exceptions handling"; |
5 | </%codemethod> | 9 | </%codemethod> |
6 | <%method void content() %> | 10 | <%method void content() %> |
7 | <h1>site-C-ing exception handling</h1> | 11 | <h1>site-C-ing exception handling</h1> |
8 | <p> | 12 | <p> |
9 | 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> |
10 | 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 |
11 | site-C-ing component goes through a few stages, namely, preprocessing, | 15 | site-C-ing component goes through a few stages, namely, preprocessing, |
12 | compiling and execution. Having three stages to go through also means the | 16 | compiling and execution. Having three stages to go through also means the |
13 | 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 |
14 | different errors. | 18 | different errors. |
15 | </p> | 19 | </p> |
16 | <p> | 20 | <p> |
17 | 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 |
18 | 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 |
19 | 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 |
20 | 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 |
21 | href="/sources/htdocs/handlers/exception_dev" title="development mode | 25 | href="/sources/htdocs/handlers/exception_dev" title="development mode |
22 | exception handler source">the exception handler component</a>. Want to <a | 26 | exception handler source">the exception handler component</a>. Want to <a |
23 | href="/exceptions/preprocess">read more</a> about preprocessor exception | 27 | href="/exceptions/preprocess">read more</a> about preprocessor exception |
24 | handling? | 28 | handling? |
25 | </p> | 29 | </p> |
26 | <p> | 30 | <p> |