🚀 go-pugleaf

skimmel@iiic.ethz.ch (Stefan Martin Kimmel) writes:

> I have a question about the large memory model. 
> 
> MS and others (Petzold) warn to use the large memory model. On the other
> hand I read that using the large memory model will make your
> code more easily portable to Windows NT.
> 
> What I heard so far about the disadvantages of the large memory model
> is not enough to stop me to try it. 
> 
> We do not need multiple instances of our application and do not 
> have to support Windows 3.0. (not even Standard Modus)
> 
> But on the other hand we want at least part of our application (the
> non-GUI part) to be easily portable to other platforms, and the 
> whole application to be easily portable to Windows NT.
> 
> Have I missed certain important considerations about the large memory 
> model? Do you know of any literature that is more encouraging about
> using the large memory model and explains more about it?
> 

Go for it... The large model eliminates a lot of problems with
Near/Far pointers, DLL interfaces, string libraries, etc.
The drawbacks are 1: single instance of your app, and 2:
a small performance penalty.  
The traditonal Windows thinking was to make the apps small
and fast and multiple instanced; these days you do what
you need to do to get it done.  
If you are going to port to WinNT, start now with at least
using the strict version of the windows.h header file,
and at best, use the Win 32s tools and start your app as a
flat memory model.  It'll be faster and more portable
to other platforms.  (and the port to NT is automatic)

- don

------------------------------------------------------------------
Don Hackler  - donh@shakala.com 
Shakala BBS (ClanZen Radio Network) Sunnyvale, CA 408-734-2289