Design and Implementation of a Documentation Tool for ... - MADOC

After forking, the child launches (or, to be exact, becomes) the process that
should be logged within doshell, while the parent does the actual input/output
logging within doio.
9 〈fork subprocesses 8c〉+≡ (7b) ⊳ 8c
if (CHILD == 0)
doshell();
else
doio();
Uses CHILD 8d, doio 33c, and doshell 31c.
Further code can be found in the appendix.
5 Evaluation
In order to show you what the code you have just seen actually does, this section
contains instructions on how to compile it, and it features an example transcript
file analyzed in detail.
5.1 Compiling forscript
forscript is written conforming to the C99 and POSIX-1.2001 standards,
with portability in mind. It has been developed on a machine running Linux
2.6.32 [6], using glibc 2.10 and GCC 4.4.3 [2]. The following command line is
an example of how to compile forscript:
gcc -std=c99 -Wl,-lrt -g -o forscript -Wall \
-Wextra -pedantic -fstack-protector-all -pipe forscript.c
To generate forscript.c out of the noweb source code, the following command
line can be used:
notangle -Rforscript.c forscript.nw > forscript.c
On the authors machine, forscript can be compiled without any compiler
warnings. It has also been successfully compiled on NetBSD.
Since Apple Mac OS X in its current version 10.6.2 lacks support for the realtime
extension of POSIX, the clock gettime() function required by forscript
is not natively available. Therefore the code described in this document can in
its current state not be compiled on OS X. However, it should be possible
to create a function emulating clock gettime() and then port forscript to
OS X.
5.2 Example Transcript File
To demonstrate forscripts output, the following pages contain a commented
hex dump of a transcript file created on the authors machine. The dump has
been created using hexdump -C transcript. Since metadata chunks do not
9