Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tcs!nujoizey!gwu
From: gwu@nujoizey.tcs.com (George Wu)
Newsgroups: comp.lang.c++
Subject: Re: Maintaining header files **and** inline management
Message-ID: <1746@tcs.tcs.com>
Date: 13 Feb 91 07:04:12 GMT
References: <15917@reed.UUCP> <3699@lupine.NCD.COM> <1991Feb5.180503.24515@mathcs.sjsu.edu>
Sender: root@tcs.com
Reply-To: gwu@nujoizey.tcs.com (George Wu)
Organization: Teknekron Communications Systems
Lines: 22

In article <1991Feb5.180503.24515@mathcs.sjsu.edu>,
horstman@mathcs.sjsu.edu (Cay Horstmann) writes:
|> In fact, the AWK script is very fast (although maybe Ron's method of
|> running diff on a header portion is faster) and I just rerun it with
|> each recompile. 
|> 
|> It doesn't matter much what method you or your shop uses for building .h
|> files, as long as it is not the manual "gosh, I guess it is time to look
|> at that .h file again" method. 

     Won't generating a new .h file with each re-compile of the .C file
cause *all* other .C files dependent upon the interface to be recompiled?
Ron preserves the original file, and hence the last modification date make
uses to determine if a recompile is necessary.  This would save a lot of
time in complex applications.

							George

----
George J Wu, Software Engineer        | gwu@tcs.com or uunet!tcs!gwu
Teknekron Communications Systems, Inc.| (415) 649-3752
2121 Allston Way, Berkeley, CA, 94704 | Quit reading news.  Get back to work.