From: "Klayhamn" Newsgroups: comp.os.msdos.djgpp References: <3f2cff90$1 AT news DOT bezeqint DOT net> Subject: Re: slow operation Date: Mon, 4 Aug 2003 03:35:31 +0200 Lines: 43 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 NNTP-Posting-Host: bzq-218-240-234.red.bezeqint.net X-Original-NNTP-Posting-Host: bzq-218-240-234.red.bezeqint.net Message-ID: <3f2da966@news.bezeqint.net> X-Trace: news.bezeqint.net 1059957094 81.218.240.234 (4 Aug 2003 03:31:34 +0300) X-Original-Trace: 4 Aug 2003 03:31:34 +0300, bzq-218-240-234.red.bezeqint.net Organization: Bezeq International Ltd. To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > Unfortunately, TurboC isn't really playing the same game. For > starters, this program is C++, not C. That makes a *big* difference. > NOTE: Borland also has a C++ compiler, but none that bears version > number 3.0 and would be able to digest ANSI Standard C++ sources. > Well i am using Borland's Turbo C 3.0 which IS able to digest ANSI c++ sources.. So we're talking about the same language/standard here and hre. > That certainly isn't making things any easier. Well i tried compiling/linking outside of RHIDE and it took me exactly the same time > To a rather significant extent, it is. Seeing that the "BEST SYSTEM" that is recommended in the site is a 700mhz Penitum - i doubt it. > Hard to tell. This could easily be a problem largely caused by > insufficient tuning of your DOS configuration. In particular, of your > disk cache settings. If the compilation time doesn't decrease by quite > a lot if you repeat the compilation from the command line at least > twice in a row: > > gpp -o Hello Hello.cpp > gpp -o Hello Hello.cpp > > your disk cache is in need of a tweak. It doesn't decreate compilation time at all, and i did exactly as the site instructed to set up disk caching.