blob: 11e992ed3f7bf5ab96eccfc043d21c00ce3370da (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
% /*@@
% @file CST.tex
% @date Wed Jan 12 14:38:29 2000
% @author Tom Goodale
% @desc
%
% @enddesc
% @version $Header$
% @@*/
\begin{cactuspart}{4}{The CST}{$RCSfile$}{$Revision$}
\renewcommand{\thepage}{\Alph{part}\arabic{page}}
\chapter{Introduction}
The CST is really the glue which holds the code together. It takes the
specifications which users have provided in their {\em .ccl} files
and generates C header and source files which are used to tell the
flesh about the thorns.
The processing is done in three stages. In the first stage the {\em .ccl}
files from each thorn in the {\em ThornList} are parsed and the data from them
is stored internally in databases. In the second stage the data is
cross-indexed for consistency. Finally the files are written out into the
{\em bindings} directory in the configuration directory.
\chapter{The Databases}
\chapter{The Generated Files}
\chapter{The Parsing Routines}
\chapter{The Output Routines}
\chapter{Miscellaneous Routines}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{cactuspart}
|
