Xref: utzoo comp.lang.c:36803 comp.software-eng:4989
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!smunews!necssd!harrison
From: harrison@necssd.NEC.COM (Mark Harrison)
Newsgroups: comp.lang.c,comp.software-eng
Subject: Re: Source File Organization
Message-ID: <688@necssd.NEC.COM>
Date: 4 Mar 91 15:03:45 GMT
References: <1210@telesoft.com>
Organization: NEC America Inc. SSD, Irving, TX
Lines: 20

In article <1210@telesoft.com>,
rlk@telesoft.com (Bob Kitzberger @sation) writes:

> Folks, the intent was to ease an existing maintenance problem.  Adding
> preprocessors such as awk or m4 into the loop only trades one maintenance
> problem for another.

That is correct, but the new maintenance problem is easier.  Our "bells
and whistles" version of the preprocessor ended up being about three
pages of AWK that hardly ever needed to be touched.  (The only times we
did touch it was to make changes in the generated troff documentation
to fit our documentation dept's. style).

Using MAKE ensured that the preprocessed files stayed in sync.  Being
able to generate documentation saved us days over the old "red-pencil"
method of dealing with our documentation group.
-- 
Mark Harrison             harrison@necssd.NEC.COM
(214)518-5050             {necntc, cs.utexas.edu}!necssd!harrison
standard disclaimers apply...