Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!iowasp.physics.uiowa.edu!ns-mx!ccad.uiowa.edu!cadsi
Newsgroups: comp.windows.ms.programmer
Subject: Re: Huge pointers in BC++
Message-ID: <1991Apr19.221458.12071@ccad.uiowa.edu>
From: cadsi@ccad.uiowa.edu (CADSI)
Date: 19 Apr 91 22:14:58 GMT
References: <1991Apr19.172703.24638@leland.Stanford.EDU>
Organization: CAD-Research, U. of Iowa, Iowa City, Iowa
Lines: 24

From article <1991Apr19.172703.24638@leland.Stanford.EDU>, by aaron@jessica.Stanford.EDU (Aaron Wallace):
> Hi!  I just got my Borland C++, and in general it looks real nice for Windows
> stuff.  I'm trying to move over some stuff from MS C 6 to BC++ and have a 
> question:  I use huge pointers a lot in my code to go through GlobalAlloc'd
> blocks of memory.  I noticed that BC++ by default implements huge pointers
> in a way that is certain to cause UAEs under protected mode.  There's a
> switch for "fast" huge pointers that may implement them correctly, but
> I can't say.  Does BC++ correctly use the __ahincr to do huge arithmetic?
> I'd assumed it does--how else could you say it does Windows if it doesn't?
> Now I'm not certain, and my program that otherwise worked fine when compiled
> with MSC dies when compiled with BC++.  Well, to be fair it only dies when it
> goes near huge pointers, but I can't be sure what the exact cause is.
> 
> If the answer is RTFM, which FM?  

As far as I know, you can't use the BC++ with its Huge pointers in Windows.
I don't have my manuals here at my office, but I do remember reading
something like this.

|----------------------------------------------------------------------------|
|Tom Hite					|  The views expressed by me |
|Manager, Product development			|  are mine, not necessarily |
|CADSI (Computer Aided Design Software Inc.	|  the views of CADSI.       |
|----------------------------------------------------------------------------|