From:	martin DOT kahlert AT keksy DOT mchp DOT siemens DOT de (Martin Kahlert)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Speed of DJGPP?
Date:	24 Jun 1997 15:11:41 GMT
Organization:	Siemens Inc.
Lines:	31
Message-ID:	<5ooo3d$h3m$1@salomon.mchp.siemens.de>
References:	<3 DOT 0 DOT 16 DOT 19970610012929 DOT 35c79ee0 AT hem1 DOT passagen DOT se>
	<5nl177$3o9a AT elmo DOT cadvision DOT com>
Reply-To:	Martin DOT Kahlert AT mchp DOT siemens DOT de
NNTP-Posting-Host:	keksy.mchp.siemens.de
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <5nl177$3o9a AT elmo DOT cadvision DOT com>,
	frenchc AT cadvision DOT com (Calvin French) writes:
> 
> Since djgpp is my only contact with any gnu-type stuff, 
> I'm just wondering about updated versions of gnu c++. 
> Are people somewhere busily working on gcc 3.0 
> (or maybe that's a bit ambitious; 
> I know the c++ working paper isn't 
> even exactly standardized yet -- let's say 2.8, 
> or whatever a significan't version update would be) or what? 
 
The next version of gcc will be 2.8.0. It will be soon out 
(this is said since about one year)
The main problem is the handling of C++ templates, I think.

> I myself can't see exactly why gcc needs 
> to use temp files, i.e., why use separate programs at all? 
> With a well defined source API which I'm sure the gnu people 
> (whoever and wherever they are) are more than capable of, 
> couldn't it all be integrated into one program while still 
> maintaining modularity? 

gcc isn't a C-compiler. It's a front end for various different
compilers (Fortran, ADA ...). It is responsible for a consistent
look and feel / consistent code generation options...
The compilers itself are called by gcc.

Under UNIX you can use pipes to eliminate the temporary files.

Hope this helps,
Martin.

- Raw text -