At 05:23 PM 3/19/01 +0000, you wrote:
>>>> Paul Kinnucan <[EMAIL PROTECTED]> 19-Mar-01 5:05:21 PM >>>
>
>>If you mean that the function that generates the
>>compile master does not save it to disk but instead
>>passes it in memory to an in-memory copy of the compiler,
>>yes, sure that is is a good idea.
>
>It's more that the target source files are passed to the compiler in
>memory or through a stream.
>
>As far as I understand it what you're doing can be expressed as a
>unix script like this:
>
> javac -cp ... @`compile-master.sh`
>
>where the script compile-master generates the filenames that need
>recompilation. I've been using that sort of system for a while and it
>works quite well. Of course it's not portable but what you're
>suggesting will be.
>
No, that is not at all what I am suggesting. This is what I am suggesting:
javac -cp... CompileMaster.java
where CompileMaster.java is generated by the Emacs lisp function
de-build-compile-masters and has the form:
// Generated by the JDE on 3/19/01.
package root;
public class CompileMaster {
ClassA f1; // reference to root.ClassA
ClassB f2; // reference to root.ClassB
...
root.pkg1.CompileMaster; // reference to subpackage pkg1.
root.pkg2.CompileMaster; // reference to subpackage pkg2.
}
- Paul