On Thu, Mar 25, 2004 at 09:48:58PM +0100, Jeroen Frijters wrote: > Etienne Gagnon wrote: > My vote is firmly against introducing macros. Unless it is done in such > a way that the resulting code is still valid Java code, so that > Classpath can still be compiled without running m4 or any of the build > scripts.
The m4 macros would only reside in the VM*.java classes, not in any other class. Firthermore, if we keep the vm/ tree around, the m4 stuff would only be in the vm/ tree, so any VM that does not want to use the m4 system (GNU m4 is highly portable and Free!!!) could get Classpath to work. We could also make sure that "make dist" builds a .tar.gz with "vanilla" VM.java files that do not need m4 to build. This is what "make dist" does in SableVM. Note that the objective is: 1- *minimal* macro stuff. 2- Maximal sharing across "ordinary" (C-based, Unix-y platform) VMs. Currently, cvs co of Classpath *DOES* require auto* tools and m4. Would that suit you? Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
