Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!think!ames!oliveb!pyramid!amdahl!cerebus!fai!wjvax!brett
From: brett@wjvax.UUCP (Brett Galloway)
Newsgroups: comp.lang.c
Subject: Re: Function prototypes (was: miscellaneous unrelated stuff)
Message-ID: <899@wjvax.wjvax.UUCP>
Date: Mon, 11-May-87 15:52:16 EDT
Article-I.D.: wjvax.899
Posted: Mon May 11 15:52:16 1987
Date-Received: Fri, 15-May-87 02:29:30 EDT
References: <18346@ucbvax.BERKELEY.EDU> <7973@utzoo.UUCP> <796@rtech.UUCP> <1821@husc6.UUCP> <2023@bunker.UUCP>
Reply-To: brett@wjvax.UUCP (Brett Galloway)
Organization: Watkins-Johnson Co., San Jose, Calif.
Lines: 19

In article <2023@bunker.UUCP> hjg@bunker.UUCP (Harry J. Gross) writes:
>	It's kind of kludgey (sp?), but if you _know_ that the only change to
>the header was the addition of a prototype that is currently unused in any other
>module, you could *touch* each of the other modules (.c and .obj).  Then make
>should leave them alone.  I have sometimes been forced to do this when I have
>added a (not currently used, but will be soon) #define to a header file that
>would otherwise cause 30 modules to recompile.

A drawback of this method is that you can inadvertently touch something that
should have been updated because of some *other* change (an error that I
have made).  I wrote a short program called 'twiddle` to store the modify
date of the argument, exec /usr/ucb/vi on it, then restore the modify date
after vi exits.  Thus, when I want to make an inocuous change to a header
file, I just 'twiddle` it.  I find that this saves much time *and* much grief.

-- 
-------------
Brett Galloway
{pesnta,twg,ios,qubix,turtlevax,tymix,vecpyr,certes,isi}!wjvax!brett