Subj : Re: out of memory
To   : borland.public.cpp.borlandcpp
From : Ed Mulroy [TeamB]
Date : Tue Jun 08 2004 03:20 pm

> Does the Borland compiler have issues
> with Win XP?

Which compiler and what version?

> I am curious to learn why a  well known compiler like
> Borland would have trouble compiling when another
> does not

I don't know what compiler or version you used.  All versions are
fairly compliant with the C and C++ language specifications while MSVC
1.52 is not.

You show no source lines and paraphrase rather than report the actual
text of errors.   There is little that can be done when information on
the problem is not given.

..  Ed

> Dparker wrote in message
> news:40c5da6b$1@newsgroups.borland.com...
>
> I recently purchased ROMDOS from Datalight which comes with a
> TCP/IP stack and was compiled with the Borland compiler. My app
> was written using MSVC 1.52, and the target is a PC-104 Pentium
> based card. I tried for two weeks to get the Borland compiler to
> compile the code and had a variety of errors relating to memory. It
> varied, but the two most common were: "compiler out of memory",
> and "too many globals". I compile everything from the command
> line in each instance.
>
> I tried a myriad of different strategies, but because of production
> demands I chose to go back to the MSVC product which does
> not exhibit the same types of errors. I am curious to learn why a
> well known compiler like Borland would have trouble compiling
> when another does not. Is Borland known to be sensitive to
> memory issues? Since the Borland compiler resides on our XP
> machine, and the MSVC compiler resides on an older Win 95
> machine I suspect that the operating system may have
> something to do with it. Does the Borland compiler have issues
> with Win XP?

.