Subj : Re: out of memory
To   : borland.public.cpp.borlandcpp
From : Dparker
Date : Tue Jun 08 2004 04:23 pm

Thank you for taking the time to respond. At some point I will put the MSVC
compiler on the XP machine and see if it too has problems, or conversely put
the Borland compiler on the Win 95 machine to see if the problems go away.

"Ed Mulroy [TeamB]" <dont_email_me@bitbuc.ket> wrote in message
news:40c6307f@newsgroups.borland.com...
> Compiler out of memory can come from being out of memory on the
> machine which I would guess comes from not having set the compatiblity
> for BC++.  Version 5.02 is from 1997.  XP is from much later.  There
> is nothing in 5.02 for compatability with XP.  Conceivably come from
> some error in the code which causes the parser to recurse past the end
> of some table but I don't think that is likely.
>
> Too much global data is different from the too many globals you had
> spoken of.  In 16 bit mode the compiler allocates a variable sized
> segment for data.  The hardware places an upper size limitation of 64K
> for a segment, larger than should be needed for a program's global and
> static data.  Those who want more can add the keyword _far to a
> declaration and the item will be placed into another segment.
>
> .  Ed
>
> > Dparker wrote in message
> > news:40c61e81$1@newsgroups.borland.com...
> >
> > Sorry for the general nature of the inquiry. The Borland
> > version is 5.02. The actual message was something
> > like: "Fatal: compiler out of memory in function main()."
> > (it gave a line number also), and at other times: "Fatal:
> > Too much global data..."
> >
> > I tried to break main() up into smaller functions but
> > because of production requirements abandoned the effort
> > in favor of the microsoft product. I have no doubt that it is
> > something that I am missing and not a fundamental
> > problem with the compiler. The command line that I
> > typed to invoke the compiler was: "bcc -w- -ml
> > filename.cpp"
>
>

.