Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!edcastle!aiai!aipna!cstr!rjc
From: rjc@cstr.ed.ac.uk (Richard Caley)
Newsgroups: comp.lang.c
Subject: Re: A question on C programming style
Message-ID: <RJC.91Apr22181050@brodie.cstr.ed.ac.uk>
Date: 22 Apr 91 18:10:50 GMT
References: <memo.942884@lynx.northeastern.edu>
Sender: news@aipna.ed.ac.uk
Organization: Centre for Speech Technology Research
Lines: 21
In-reply-to: cschmidt@lynx.northeastern.edu's message of 20 Apr 91 23:00:35 GMT


[Slightly off C but...]

In article <memo.942884@lynx.northeastern.edu>, cschmidt  (c) writes:

c> One obvious advantage to this approach is that the dependency list is
c> always guaranteed to be up to date.  When using a conventional
c> dependency generator, there is a temptation to postpone using it.

There is another (IMHO better) solution. The Makefile can arrange for
the dependencies to be recalculated when necessary, that is after all
what make is good for.

You need a make which understands `include' directives, but after that
it is relatively painless.  

Details left as an excorcise.

--
rjc@cstr.ed.ac.uk			_O_
					 |<