Re: dependency scanner

Lew wrote:
> Aryeh M. Friedman wrote:
>> C does at least has a trivial way to find depends (#include)
> 
> Huh?  What does #include have to do with managing object file
dependencies?
> 
> If you recompile foo.c and bar.o depends on foo.o, nothing in C is going

> to help you figure that one out, via #include or otherwise.  You need 
> make for that.
> 
> #include is a *pre*-processing step; it happens before the compilation 
> even looks at the source code.  There is no equivalent in Java.  The 
> 'im****t' directive does not include anything at all; it just helps the 
> compiler with name resolution.

What he means is that some compilers (such as gcc) have sup****t for 
generating dependency information based on #include statements. IIRC the 
-M flag will cause gcc to write out a file describing what objects 
depend on what source files based on the knowledge it obtains through 
parsing. BTW there used to be a similar tool for Java (JavaDeps?) but I 
have no idea if it's still around.

RM