Mail Archives: djgpp/1995/12/20/22:19:48
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:3966
|
Path: | news-dnh.mv.net!mv!barney.gvi.net!news.netrail.net!imci2!newsfeed.internetmci.com!news.internetMCI.com!darwin.sura.net!gwu.edu!seas.gwu.edu!james
|
From: | james AT seas DOT gwu DOT edu (James Sally)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: topline in v2
|
Date: | 20 Dec 1995 02:46:26 GMT
|
Organization: | George Washington University
|
Lines: | 17
|
Message-ID: | <4b7te2$h9t@cronkite.seas.gwu.edu>
|
References: | <DJu3It DOT 2Eu AT jade DOT mv DOT net>
|
NNTP-Posting-Host: | 128.164.9.3
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:
: Btw, what would you do with any other compiler to see it's progress?
Since you asked, Borland's (in Windows at least) shows the number of
lines processed. So as long as the number keeps rising, then I know the
compiler is doing something.
The topline indicator has also helped me in just setting up my dos
environment under Win95, since it showed how much memory was left during
compilation. But primarily, it has also showed what sub-program the code
crashed under (which it did from time to time).
So, to me, the topline was a convienience, and something that I liked
in DJGPP compared to other compilers, but I can live without it :(
Later,
Jim
- Raw text -