Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!uwm.edu!bionet!agate!stanford.edu!leland.Stanford.EDU!aaron@jessica.Stanford.EDU
From: aaron@jessica.Stanford.EDU (Aaron Wallace)
Newsgroups: comp.windows.ms.programmer
Subject: Huge pointers in BC++
Message-ID: <1991Apr19.172703.24638@leland.Stanford.EDU>
Date: 19 Apr 91 17:27:03 GMT
Sender: Aaron Wallace
Reply-To: aaron@jessica.Stanford.EDU (Aaron Wallace)
Organization: Stanford University
Lines: 17

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?  

Thanks in advance!

Aaron Wallace