From: "Lars Hansen" <lars DOT o DOT hansen AT gmx DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: several questions (symify, dynamic labels, cpu clock)
Date: Tue, 21 Jan 2003 17:27:08 +0100
Organization: 1&1 Internet AG
Lines: 29
Message-ID: <b0jsct$8l9$1@news.online.de>
References: <b0ff15$lql$1 AT news DOT online DOT de> <b0je70$5ui$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <b0jp6g$7b9$1 AT news DOT online DOT de> <200301211558 DOT h0LFwcF16138 AT envy DOT delorie DOT com>
NNTP-Posting-Host: p50838960.dip0.t-ipconnect.de
X-Trace: news.online.de 1043166429 8873 80.131.137.96 (21 Jan 2003 16:27:09 GMT)
X-Complaints-To: abuse AT online DOT de
NNTP-Posting-Date: 21 Jan 2003 16:27:09 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> If you look up clock() in the manual (RTFM = Read The F* Manual) it
> tells you what CLOCKS_PER_SEC is.  Or if you look at the comment for
> CLOCKS_PER_SEC in <time.h> you'd see that it's a constant (91) so it
> obviously isn't the CPU speed.
>
> Type "info libc a clock" at the DOS prompt.


Yes, thanks (it's the same information as in your C library reference)
(actually it tells me that its used to convert clock() return value to seconds
but I don#t wether clicks is cpu clock ticks or some other timer ticks) and
you're right: that it is a constant and therefore probably not the CPU speed
of the cpu the code is executed on could also be derived from it being written
UPPERCASE.


I'll try to use info more and the extra doc formats I just downloaded seem
also to be useful (though they are just the offline version of their online
pendants at gcc.gnu.org for example) - but a "quick" overview of gcc, gpp (or
g++?), symify etc. in ONE file as djgpp doc. woudn't be bad. I could do that,
but i must "learn" them first myself and that needs time I don't have much
(but sometimes perhaps); also the one "offering" djgpp probably knows more and
might be interested in that doc type himself (as it might be just THE doc
needed for a comman-line dev.env djgpp is) - so you (not to be read in an
"harsh" emphasis)

Lars