>OK, there is one problem! What if a particularly clever developer, decides to >not "copy" or make a new file with the same name as the old one "foobar.h". >But instead, if he does
>mv include1/foo.h include1/foobar.h -------------------- Well, I think this is not my problem, but the developers (I am actually a C developer too, it's just that right now I wear a make hat)! Even in a very simple makefile, if the user decides to "mv" and not edit anything, they better be aware, that the timestamp may be old, and so make will not remake anything that depends on what they moved. So I think it is OK not to remake in that case. Semantics of the OS... "move" system call. Mark _______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
