Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site dataioDataio.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!uw-june!entropy!dataio!bright
From: bright@dataioDataio.UUCP (Walter Bright)
Newsgroups: net.lang.c,net.micro.pc
Subject: Re: More on MIX C
Message-ID: <857@dataioDataio.UUCP>
Date: Mon, 11-Nov-85 12:54:45 EST
Article-I.D.: dataioDa.857
Posted: Mon Nov 11 12:54:45 1985
Date-Received: Wed, 13-Nov-85 08:15:47 EST
References: <429@sii.UUCP> <218@mips.UUCP>
Reply-To: bright@dataio.UUCP (Walter Bright
Organization: Data I/O Corp., Redmond WA
Lines: 16
Xref: watmath net.lang.c:7024 net.micro.pc:5828

In article <218@mips.UUCP> kim@mips.UUCP (Kim DeVaughn) writes:
>> 	- There is no mechanism for linking assembler programs to the C
>> 	  programs.  There *is* a mechanism for calling assembler programs,
>I talked to the MIX.C folk the other day on this very point.  The person
>I spoke to told me that they would have a utility very soon (actually, he
>said "in a couple of weeks") to convert Intel/Microsoft .obj format files
>into something the MIX linker could handle.

I am constantly surprised why compiler vendors keep inventing their own
.obj file formats. It complicates life for both the vendor and the
customer. The vendor has to write a linker and librarian, and perpetually
try to help people who want to link in assembler or Fortran modules. The
customer has to continually deal with a 'kludge' and object file
conversion programs.
The Intel .obj format isn't a secret either, Intel publishes a spec for
it (though I would vote it for the 'Most Obtuse Document' award).