summaryrefslogtreecommitdiffabout
path: root/htdocs/exceptions/compile.chtml
authorMichael Krelin <hacker@klever.net>2005-04-03 11:49:01 (UTC)
committer Michael Krelin <hacker@klever.net>2005-04-03 11:49:01 (UTC)
commitd3e8a3f68b62668af9bc992e94dfb3c822d270dc (patch) (side-by-side diff)
tree87a5f43f5075dcfc0c0033a4ca50eb990d498e70 /htdocs/exceptions/compile.chtml
parent85471d7c2c74035399ba7047f409fe6248e1d6f0 (diff)
downloadsitecing-d3e8a3f68b62668af9bc992e94dfb3c822d270dc.zip
sitecing-d3e8a3f68b62668af9bc992e94dfb3c822d270dc.tar.gz
sitecing-d3e8a3f68b62668af9bc992e94dfb3c822d270dc.tar.bz2
made use of pragma main
Diffstat (limited to 'htdocs/exceptions/compile.chtml') (more/less context) (ignore whitespace changes)
-rw-r--r--htdocs/exceptions/compile.chtml3
1 files changed, 2 insertions, 1 deletions
diff --git a/htdocs/exceptions/compile.chtml b/htdocs/exceptions/compile.chtml
index 68dd034..94bd2e1 100644
--- a/htdocs/exceptions/compile.chtml
+++ b/htdocs/exceptions/compile.chtml
@@ -1,34 +1,35 @@
-% html(); return; /* vim:set ft=sitecing: */
+% /* vim:set ft=sitecing: */
%%derive layout = "/ancestry/layout.chtml";
+%%pragma main=page
<%constructor>
b_strict = false;
PN_PREV("/exceptions/preprocess","preprocess","preprocessing errors");
PN_NEXT("/exceptions/runtime","runtime","runtime exceptions");
</%constructor>
<%codemethod string title() %>
return "compile-time exceptions handling";
</%codemethod>
<%method void content() %>
<h1>site-C-ing compile-time exception handling</h1>
<p>
Similar to <a href="/exceptions/preprocess">preprocessing exceptions</a>
there is a wide range of errors you may put into your code which will pass
through preprocessor and will be caught later at the compile-time.
</p>
<p>
Once you complete writing your <a
href="/view/htdocs/exceptions/development/compile.chtml" target="insert"
title="the link opens in the frame below">erroneous code</a> and
<em>site-C-ing</em> is done preprocessing it, it will feed the preprocessed
code into c++ compiler which will refuse to compile the code like this. This
is where <a href="/view/htdocs/handlers/exception_dev" target="insert"
title="the link opens in the frame below">the exception 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>, takes over the process and gives you <a
href="/exceptions/development/compile" target="insert" title="the link opens
in the frame below">the report</a>. Like with any handler, you may wish to
set some <a href="/view/htdocs/handlers/exception_prod" target="insert"
title="the link opens in the frame below">different handler</a> in your <a
href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the
link opens in the frame below">production configuration</a>, which just gives