1 files changed, 2 insertions, 0 deletions

diff --git a/htdocs/exceptions/compile.chtml b/htdocs/exceptions/compile.chtml
index aa4c8df..68dd034 100644
--- a/htdocs/exceptions/compile.chtml
+++ b/htdocs/exceptions/compile.chtml
@@ -1,28 +1,30 @@
 % html(); return; /* vim:set ft=sitecing: */
 %%derive layout = "/ancestry/layout.chtml";
 <%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