Wes Biggs writes:
> I think explicit imports help readability anyway
Agreed.
> of the classes to check). The utility would look for "import x.y.z",
> check if the file x/y/z.java exists, and if so insert a make dependency
> line for x/y/z.class accordingly.
Taking the current classpath into account. A change of the
classpath would result in different dependencies.
> to import gnu.java.Config (replace with wherever Config.java lives).
John wanted to avoid editing a Config file. Either Config.java
is created automatically (Config.java.in?), or the classpath
is switched for different builds, picking a different location
of config? gnu_debug.java.Config?
> Do we want these utils to be java apps or does it matter?
Personally, I would prefer Java, and to address bootstrap,
a Java2C generated C source in the distribution. But I am not
doing the work, so this is just asking for Santa.
b.
