Diffstat (limited to 'htdocs/exceptions/compile.chtml') (more/less context) (ignore whitespace changes)
-rw-r--r-- | htdocs/exceptions/compile.chtml | 3 |
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,52 +1,53 @@ | |||
1 | % html(); return; /* vim:set ft=sitecing: */ | 1 | % /* vim:set ft=sitecing: */ |
2 | %%derive layout = "/ancestry/layout.chtml"; | 2 | %%derive layout = "/ancestry/layout.chtml"; |
3 | %%pragma main=page | ||
3 | <%constructor> | 4 | <%constructor> |
4 | b_strict = false; | 5 | b_strict = false; |
5 | PN_PREV("/exceptions/preprocess","preprocess","preprocessing errors"); | 6 | PN_PREV("/exceptions/preprocess","preprocess","preprocessing errors"); |
6 | PN_NEXT("/exceptions/runtime","runtime","runtime exceptions"); | 7 | PN_NEXT("/exceptions/runtime","runtime","runtime exceptions"); |
7 | </%constructor> | 8 | </%constructor> |
8 | <%codemethod string title() %> | 9 | <%codemethod string title() %> |
9 | return "compile-time exceptions handling"; | 10 | return "compile-time exceptions handling"; |
10 | </%codemethod> | 11 | </%codemethod> |
11 | <%method void content() %> | 12 | <%method void content() %> |
12 | <h1>site-C-ing compile-time exception handling</h1> | 13 | <h1>site-C-ing compile-time exception handling</h1> |
13 | <p> | 14 | <p> |
14 | Similar to <a href="/exceptions/preprocess">preprocessing exceptions</a> | 15 | Similar to <a href="/exceptions/preprocess">preprocessing exceptions</a> |
15 | there is a wide range of errors you may put into your code which will pass | 16 | there is a wide range of errors you may put into your code which will pass |
16 | through preprocessor and will be caught later at the compile-time. | 17 | through preprocessor and will be caught later at the compile-time. |
17 | </p> | 18 | </p> |
18 | <p> | 19 | <p> |
19 | Once you complete writing your <a | 20 | Once you complete writing your <a |
20 | href="/view/htdocs/exceptions/development/compile.chtml" target="insert" | 21 | href="/view/htdocs/exceptions/development/compile.chtml" target="insert" |
21 | title="the link opens in the frame below">erroneous code</a> and | 22 | title="the link opens in the frame below">erroneous code</a> and |
22 | <em>site-C-ing</em> is done preprocessing it, it will feed the preprocessed | 23 | <em>site-C-ing</em> is done preprocessing it, it will feed the preprocessed |
23 | code into c++ compiler which will refuse to compile the code like this. This | 24 | code into c++ compiler which will refuse to compile the code like this. This |
24 | is where <a href="/view/htdocs/handlers/exception_dev" target="insert" | 25 | is where <a href="/view/htdocs/handlers/exception_dev" target="insert" |
25 | title="the link opens in the frame below">the exception handler</a>, | 26 | title="the link opens in the frame below">the exception handler</a>, |
26 | specified in <a href="/view/htdocs/exceptions/development/.scrc" | 27 | specified in <a href="/view/htdocs/exceptions/development/.scrc" |
27 | target="insert" title="the link opens in the frame below">the configuration | 28 | target="insert" title="the link opens in the frame below">the configuration |
28 | file</a>, takes over the process and gives you <a | 29 | file</a>, takes over the process and gives you <a |
29 | href="/exceptions/development/compile" target="insert" title="the link opens | 30 | href="/exceptions/development/compile" target="insert" title="the link opens |
30 | in the frame below">the report</a>. Like with any handler, you may wish to | 31 | in the frame below">the report</a>. Like with any handler, you may wish to |
31 | set some <a href="/view/htdocs/handlers/exception_prod" target="insert" | 32 | set some <a href="/view/htdocs/handlers/exception_prod" target="insert" |
32 | title="the link opens in the frame below">different handler</a> in your <a | 33 | title="the link opens in the frame below">different handler</a> in your <a |
33 | href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the | 34 | href="/view/htdocs/exceptions/production/.scrc" target="insert" title="the |
34 | link opens in the frame below">production configuration</a>, which just gives | 35 | link opens in the frame below">production configuration</a>, which just gives |
35 | user <a href="/exceptions/production/preprocess" target="insert" title="the | 36 | user <a href="/exceptions/production/preprocess" target="insert" title="the |
36 | link opens in the frame below">a friendly yet lame excuse</a>. | 37 | link opens in the frame below">a friendly yet lame excuse</a>. |
37 | </p> | 38 | </p> |
38 | <p class="note"> | 39 | <p class="note"> |
39 | Note, that these output pages are fakes -- I do not want to spawn the | 40 | Note, that these output pages are fakes -- I do not want to spawn the |
40 | compiler each time you want to see the output and put this unnecessary load | 41 | compiler each time you want to see the output and put this unnecessary load |
41 | on cpu. These static pages are in fact saved output of the real exception | 42 | on cpu. These static pages are in fact saved output of the real exception |
42 | handlers. | 43 | handlers. |
43 | </p> | 44 | </p> |
44 | 45 | ||
45 | <div class="insert"> | 46 | <div class="insert"> |
46 | <iframe id="insert" name="insert" src="about:blank" width="95%" height="300"> | 47 | <iframe id="insert" name="insert" src="about:blank" width="95%" height="300"> |
47 | <p>I wanted to put an <iframe> here, but your browser does not seem to | 48 | <p>I wanted to put an <iframe> here, but your browser does not seem to |
48 | support it. That is okay, it still will open links somehow.</p> | 49 | support it. That is okay, it still will open links somehow.</p> |
49 | </iframe> | 50 | </iframe> |
50 | </div> | 51 | </div> |
51 | 52 | ||
52 | </%method> | 53 | </%method> |