Xref: utzoo comp.lang.c:7558 comp.sys.ibm.pc:12397
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!well!mccarthy
From: mccarthy@well.UUCP (Patrick McCarthy)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: MSC Danger (was Re: Turbo C vs Quick C)
Message-ID: <5299@well.UUCP>
Date: 25 Feb 88 05:39:38 GMT
References: <389@lscvax.UUCP> <567@naucse.UUCP> <2946@dasys1.UUCP> <5441@cit-vax.Caltech.Edu> <1082@dutesta.UUCP>
Reply-To: mccarthy@well.UUCP (Patrick McCarthy)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 15
Keywords: near far large small mixed



In article 7731 of comp.lang.c knop@dutesta.UUCP (Peter Knoppers) writes:

> Why, oh why don't the .obj files in MSDOS contain some bits telling
> the linker whether a function in the .obj file expects to be called
> with a FAR or a NEAR call. This can prevent accidentally linking
> modules compiled for different models.

Fortunately, most of the time this will result in fixup overflow errors
at link time. Using make is an excellent way to avoid this problem
altogether (though many consider it a major pain for single module
programs).

Pat McCarthy
Reply: mccarthy@well.UUCP