From: broeker AT acp3bf DOT knirsch DOT de (Hans-Bernhard Broeker) Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP (gcc) and Borland IDE Date: 29 Aug 1999 20:58:49 +0200 Organization: RWTH Aachen, III. physikalisches Institut B Lines: 19 Message-ID: <7qbvt9$1q3@acp3bf.knirsch.de> References: NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 935953136 4256 137.226.32.75 (29 Aug 1999 18:58:56 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 29 Aug 1999 18:58:56 GMT X-Newsreader: TIN [version 1.2 PL2] To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote: > On Thu, 26 Aug 1999, =?iso-8859-1?Q?Fran=E7ois?= Jacques wrote: > > They would have two compiler editions? One > > embedded in the IDE and one command line? > Yes, precisely. Not enough that they have two of them; those two also behave differently, in some situations. E.g. I have a program that can only be built with the command line version of Borland C++ 3.1. The 'integrated' compiler bombs on the same program, complaining about an internal table size being overflown --- And a later version of the compiler wouldn't compile that same program *at all*, neither the integrated nor the command-line version... -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.