Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!nuchat!moray!urchin!p6.f506.n106.z1.fidonet.org!Bob.Stout
From: Bob.Stout@p6.f506.n106.z1.fidonet.org (Bob Stout)
Newsgroups: comp.lang.c++
Subject: Re: Turbo C++ vs. Zortec 2.1
Message-ID: <1129.26B0EC73@urchin.fidonet.org>
Date: 26 Jul 90 16:56:28 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/506.6 - Fulcrum's Edge, Spring TX
Lines: 15

In a message of <Jul 26 03:55>, timothy.j.thompson (tjt@cbnewsh.att.com ) 
writes: 
 >> What are peoples experiences with Turbo C++ and ZOrtech C++, in particular
 >> their  use of extended and expanded memory?
 >
 >I've successfully used the __handle pointer in Zortech C/C++ to access
 >expanded memory (although only with certain expanded memory managers)
 >to get (much) more than 640K of data.   I've only read the glossy
 >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++ ?

  VROOMM only overlays code, not data. TC++ currently has no inbuilt support of 
virtual data. ZTC++ 2.1 includes VCM, not as slickly named as VROOM, but better 
designed, IMHO. Both VCM and VROOMM are overlay managers for code only.