Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!aero!aerospace.aero.org!slewis
From: slewis@aerospace.aero.org
Newsgroups: comp.windows.ms
Subject: Pleasures and Penanties of the Large Model
Message-ID: <82934@aerospace.AERO.ORG>
Date: 4 Sep 90 17:06:28 GMT
Sender: news@aerospace.aero.org
Reply-To: slewis@aerospace.aero.org ()
Organization: The Aerospace Corporation, El Segundo, CA
Lines: 13


	The documentation on MS Windows advises against the use of the large
model. I understand the dangers of locking down large blocks. There are
other reasons for using the large model. In porting code between other
systems and Windows, there is a common assumption in most C's that there
is only one type of pointer. Going to the large model forces all pointers to
be far pointers (I think for this discussion we can ignore the differences in
speed between accessing near and far pointers.). Forcing all pointers
to be far pointers greatly simplifies the management of code.
	If I have a well behaved application which requires say about 10K of
local storage and 200K global storage which it manages with the GlobalAlloc
mechanism, is there any real penalty in specifying the large model and buying
a great simplification on my pointer management???