Rainer Deyke wrote:
Yigal Chripun wrote:
oh, I forgot my last point:
for C link-time compatibility you need to be able to _read_ C object
files and link them to your executable. you gain little from the ability
to _write_ object files.
You can transitivity. Two compilers for different languages that both
produce C object files can link to each other; two compiler that can
only read C object files cannot.
good point.
if you want to do a reverse integration (use D code in your C project)
you can and IMO should have created a library anyway instead of using
object files and the compiler should allow this as a separate option via
a flag, e.g. --make-so or whatever
If you can read and write compatible library files, you don't need to
read or write compatible object files, since library files can take the
place of object files.
that's even better. just allow 2-way usage of C libs and that's it. no
need to support the C object file formats directly.
