Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!waikato.ac.nz!comp.vuw.ac.nz!cavebbs!frank
From: frank@cavebbs.gen.nz (Frank van der Hulst)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Mixed Memory Model Libraries
Message-ID: <1991May29.073937.21280@cavebbs.gen.nz>
Date: 29 May 91 07:39:37 GMT
References: <1521@rust.zso.dec.com>
Organization: The Cave MegaBBS, Public Access Usenet, Wellington, NZ
Lines: 25

In article <1521@rust.zso.dec.com> mtp@mold.zso.dec.com (Mike Peterson) writes:
>
>    I want to build a large memory model library against which small model
>    applications may link.  My question is around the multiple modules that
>    comprise the library.  For example,  the library FOO.LIB is built from the

ne problem I've come across in attempting to do this is that your routines
must not call any of C's library routines... otherwise all the addresses 
(generated by the call as 32 bits, but expected by the small library
routines to be 16 bits) will be screwed up.
>    			
>    I want the routines in bar.c and misc.c to be NEAR with respect to
>    foo.c and each other (Apart from those internal routines that call
>    public services).

C
You must use the keyword 'near' or 'far' for all addresses, and also you must use
prototypes which include 'near' or 'far'.
>


-- 

Take a walk on the wild side, and I don't mean the Milford Track.
Kayaking: The art of appearing to want to go where your boat is taking you.