Swaroop does not yet realize it, but he is beginning to ask "what should
the bitcc command line look like, and how should modules be resolved?"
My intention for this generation of the compiler is that the bitcc
command line should take the form:
bitcc -Idir ... -Idir -e module.name.fcn-name
This is the "whole program compilation" mode. The meaning of this
command line is that the compiler should begin by importing
"module.name", and should recursively import, as needed, any module that
must therefore be imported.
In order to resolve the module name "a.b.c", the compiler will proceed
in strict left-to-right order across the -I directories, attempting to
find a file named "a.b.c.bitc".
The first file found proceeding left to right wins.
This approach has worked very well for CapIDL.
When we eventually do separate compilation, we will also support a
command line of the form
bitcc -Idir ... -Idir module.name module2.name ...
This means that the modules named on the command line should be compiled
to .o files, importing as needed from the -I directories.
There are some details to be straightened out here, but the basic
approach will work okay.
shap
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
