author | Michael Krelin <hacker@klever.net> | 2005-02-03 00:17:58 (UTC) |
---|---|---|
committer | Michael Krelin <hacker@klever.net> | 2005-02-03 00:17:58 (UTC) |
commit | d379841850daab4693d596784b790b13e20e3a03 (patch) (side-by-side diff) | |
tree | eafa246cd99308ea349aef90a708ef9f6d7a0418 /htdocs/exceptions/preprocess.chtml | |
parent | 870963df2dac72e433fd7f94cd1cccc8cd6ea2d0 (diff) | |
download | sitecing-d379841850daab4693d596784b790b13e20e3a03.zip sitecing-d379841850daab4693d596784b790b13e20e3a03.tar.gz sitecing-d379841850daab4693d596784b790b13e20e3a03.tar.bz2 |
1. added a 'browse-through' navigation
2. improved performance by passing -flush to FastCgiExternalServer
3. emphasized links in text
Diffstat (limited to 'htdocs/exceptions/preprocess.chtml') (more/less context) (show whitespace changes)
-rw-r--r-- | htdocs/exceptions/preprocess.chtml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/htdocs/exceptions/preprocess.chtml b/htdocs/exceptions/preprocess.chtml index 8516139..88b8741 100644 --- a/htdocs/exceptions/preprocess.chtml +++ b/htdocs/exceptions/preprocess.chtml @@ -1,28 +1,30 @@ % html(); return; /* vim:set ft=sitecing: */ %%derive layout = "/ancestry/layout.chtml"; <%constructor> b_strict = false; + PN_PREV("/exceptions","exceptions","exception handling overview"); + PN_NEXT("/exceptions/compile","compile-time","compile-time errors"); </%constructor> <%codemethod string title() %> return "preprocessor exceptions handling"; </%codemethod> <%method void content() %> <h1>site-C-ing preprocessor exception handling</h1> <p> It was one of those days when you just can't type right and can't think of what you're typing. It is not unusual that, under such circumstances, you end up with a code like <a href="/view/htdocs/exceptions/development/preprocess.chtml" target="insert" title="the link opens in the frame below">this</a> -- by the time you were about to close your <code><%code></code> block you were thinking about some constructor in some component elsewhere in the universe. </p> <p> <em>site-C-ing</em> parser will see the inconsistency and throw an exception which will be caught and passed to <a href="/view/htdocs/handlers/exception_dev" target="insert" title="the link opens in the frame below">the handler</a>, specified in <a href="/view/htdocs/exceptions/development/.scrc" target="insert" title="the link opens in the frame below">the configuration file</a>, which will produce some nice, human-readable <a href="/exceptions/development/preprocess" target="insert" title="the link opens in the frame below">output</a>. Well, |