Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!helios.ee.lbl.gov!ncis.tis.llnl.gov!lll-winken!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.lang.c
Subject: Re: Memory Models
Keywords: Memory models,C
Message-ID: <3160@scolex.sco.COM>
Date: 12 Aug 89 04:41:18 GMT
References: <562@dcscg1.UUCP> <10703@smoke.BRL.MIL>
Reply-To: seanf@scolex.UUCP (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 13

In article <10703@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>Unless you have a strong reason not to,
>just always use the large memory model.  (A strong reason would be
>compatibility with an existing object library, for example.)

Another one would be speed and size of executables.

Using large-model is slower than small model, sometimes considerably.

-- 
Sean Eric Fagan  |    "Uhm, excuse me..."
seanf@sco.UUCP   |      -- James T. Kirk (William Shatner), ST V: TFF
(408) 458-1422   | Any opinions expressed are my own, not my employers'.