Xref: utzoo comp.lang.c:30587 comp.lang.c++:8643
Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!mintaka!yale!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!mejia
From: mejia@cs.umn.edu (John C. Mejia)
Newsgroups: comp.lang.c,comp.lang.c++
Subject: Re: Turbo C++ vs. Zortec 2.1
Message-ID: <1990Jul27.184029.7317@cs.umn.edu>
Date: 27 Jul 90 18:40:29 GMT
References: <2225@vela.acs.oakland.edu> <1990Jul26.035511.3640@cbnewsh.att.com>
Organization: University of Minnesota, Minneapolis - CSCI Dept.
Lines: 25

In article <1990Jul26.035511.3640@cbnewsh.att.com> tjt@cbnewsh.att.com
(timothy.j.thompson) writes: ....stuff deleted >descriptions of Turbo
C++, but it sounds like its VROOM (is that right?)  >stuff only
applies to the *text* of a program, not the *data*.  >Can you get
access to more than 640K of *data* with Turbo C++ ?  > ...Tim
Thompson...tjt@twitch.att.com...  

Sure, just use one of the larger memory models.  This gives you access
to up to 1MB of code or data (depending on the memory model) but after
that, I'm not sure what (if anything) VROOM will do if you need more
than 1MB of data.  As for code, I understand it automatically takes
care of this overlay stuff.

-------------------------------------------------------------------------------
                               John C. Mejia
E-MAIL (in order of preference)                                    VOICE
mejia@cs.umn.edu                                              612-625-8348 (W)
mejia%csfsa.cs.umn.edu@umn-cs.cs.umn.edu                      612-338-7336 (H)
                                               / F
                                  __o         / I
               __o              -\<,         / N
              -\<,  ...........O / O        / I
..............O/ O                         / S
                                          / H
-------------------------------------------------------------------------------