| -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 @@ -1,32 +1,32 @@ % html(); return; /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; <%constructor> PN_PREV("/simple","simple page","building a really simple page"); PN_NEXT("/exceptions/preprocess","preprocess","preprocessing errors"); </%constructor> <%codemethod string title() %> return "exceptions handling"; </%codemethod> <%method void content() %> <h1>site-C-ing exception handling</h1> <p> The purpose of this section is to give an overview of the <em>site-C-ing</em> exception handling mechanism. Before the web visitor can see the page each site-C-ing component goes through a few stages, namely, preprocessing, - compiling and execution. Having three stages to go through also means the + compiling and execution. Having three stages to go through also means three stages one can fail to go through and three exciting opportunities to handle different errors. </p> <p> First each component is preprocessed so that you can feed the valid c++ code to the compiler. Here is where the preprocessor can choke at your broken source code. Once preprocessor failes to parse your code it will throw an exception which <em>site-C-ing</em> will catch and pass to <a href="/sources/htdocs/handlers/exception_dev" title="development mode exception handler source">the exception handler component</a>. Want to <a href="/exceptions/preprocess">read more</a> about preprocessor exception handling? </p> <p> After the preprocessing stage is over we have a great opportunity to catch the compile-time errors. After <em>site-C-ing</em> fails to compile the |