Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Borland C++ problem.
Message-ID: <6384@bwdls58.bnr.ca>
Date: 5 Apr 91 14:06:04 GMT
References: <149000018@eriador>
Sender: news@bwdls58.bnr.ca
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 29

In article <149000018@eriador> mguyott@eriador.prime.com writes:
<
<    Compiler table limit exceeded.
<
<We called Borland and they told us our program was too complex and we
<should make it simplier!  That was a lot of help!  We managed to get

Just break up the module that produced the message into a couple of smaller
modules.  Does the error also occur when using the "x" version of the compiler?

Alternatively, one could avoid this entire mess by simply coding your own
version of the int86x() routine to replace the "broken" Zortech one.  This is
a *really* simply piece of code to write.

<The error generated is:
...details omitted...
On the off chance that the compiler really *did* find an error,
try using:

... = MakeProcInstance(int(far pascal*)ConnectDlgProc,(unsigned int)hInstParent)
                                     ^
or maybe again without the star      |
-- 
MLORD@BNR.CA  Ottawa, Ontario *** Personal views only ***
begin 644 NOTSHARE.COM ; Free MS-DOS utility - use instead of SHARE.EXE
MZQ.0@/P/=`J`_!9T!2[_+H``L/_/+HX&+`"T2<TAO@,!OX0`N1(`C,B.P/.DS
<^K@A-<TAB1Z``(P&@@"ZA`"X(27-(?NZE@#-)P#-5
``
end