Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!labrea!rutgers!njin!princeton!phoenix!pucc!BVAUGHAN
From: BVAUGHAN@pucc.Princeton.EDU (Barbara Vaughan)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran graphics
Message-ID: <7139@pucc.Princeton.EDU>
Date: 10 Feb 89 16:37:40 GMT
References: <4328@hubcap.UUCP> <4869@xenna.Encore.COM>
Reply-To: BVAUGHAN@pucc.Princeton.EDU
Distribution: usa
Organization: Princeton University, NJ
Lines: 23
Disclaimer: Author bears full responsibility for contents of this article

In article <4869@xenna.Encore.COM>, kaufman@maxzilla.Encore.COM (Lar Kaufman) writes:

>In article <4328@hubcap.UUCP> rajohn@hubcap.UUCP (r alan johnson) writes:
>>This may be a stupid question, but since the Microsoft FORTRAN 4.1
>>compiler tells me that it is possible to link Microsoft C object files,
>>is is just as possible to link Turbo C 1.5 object files? I want the Turbo C
>> An object file is an object file isn't it?                                                    ated!
>
>Your best bet to marry Microsoft Fortran with Turbo C is probably a
>third-party product designed for the purpose. I suggest Phoenix
>Technologies' PLink-86 (or whatever is most current).

This is not true; in my previous followup to this posting,
I explained why. I have PLink-86 Plus, and I quote from their
manual:  "Do not mix and match object files from different compilers.
Unlike mainframe compilers, microcomputer compilers are often incom-
patible with each other. PLink86 plus will link the programs and tell
you about addressing problems, but there is no way for the linker
to know if the run-time systems of the two languages can coexist."
The Microsoft linker and the IBM linker will do the same.  If and only
if a comiler claims to produse object code compatible with that of
another compiler should you attempt to link the two. Even then, as I
said before, you usually must use a restricted subset of both languages.