Path: utzoo!utgpu!cunews!bnrgate!bigsur!bnr-rsc!bcarh181!schow
From: schow@bcarh181.bnr.ca (Stanley T.H. Chow)
Newsgroups: comp.software-eng
Subject: Re: Source File Organization
Message-ID: <4080@bnr-rsc.UUCP>
Date: 1 Mar 91 19:07:32 GMT
References: <1991Feb26.045242.23453@rfengr.com> <8001@aspect.UUCP>
Sender: news@bnr-rsc.UUCP
Reply-To: bcarh185!schow@bnr-rsc.UUCP (Stanley T.H. Chow)
Organization: BNR Ottawa, Canada
Lines: 18
Summary:
Followup-To:
Keywords:

In article <8001@aspect.UUCP> dave@aspect.UUCP (Dave Corcoran) writes:
>In article <1991Feb26.045242.23453@rfengr.com>, rfarris@rfengr.com (Rick Farris) writes:
>  [problem deleted]
>
>run this through m4 you might be pleasantly suprised; although anyone
>maintaining your code may what to drop the adjective "pleasantly" :-)
 [solution using m4 macro deleted]

Yet another solution is to "audit" the data. This can be done in the
initialization phase or by a standalone program. You could even go as
far as putting the audit program in your make file so that a "mismatch"
will stop the make. This is not as good as the compiler catching it,
but is a close second.

Stanley Chow        BitNet:  schow@BNR.CA
BNR		    UUCP:    ..!uunet!bnrgate!bcarh185!schow
(613) 763-2831               ..!psuvax1!BNR.CA.bitnet!schow
Me? Represent other people? Don't make them laugh so hard.