Date:	Sun, 11 May 1997 12:21:41 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Michael Mauch <mauch AT unidui DOT uni-duisburg DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: testing uclock()
In-Reply-To:	<337b45ba.21833362@news.uni-duisburg.de>
Message-ID:	<Pine.SUN.3.91.970511122103.27751O-100000@is>
MIME-Version:	1.0

On Fri, 9 May 1997, Michael Mauch wrote:

> > I'm not sure I understand.  Is that performance good enough to live up to 
> > the docs of `uclock' when it is called from Windows?
> 
> Yes, but calling puclock() from Win95 takes about 10 times longer than
> from DOS.

Tough.

> Thanks for your explanation of __bss_count. I guess this should be
> changed in puclock, too. Shall I repost the whole thing?

I think so, yes.

> I will try to not uuencode it this time (sorry for that).

Good idea.

> But the implementation of usleep() uses the clock() function with its
> 55ms resolution, so usleep() cannot even have millisecond resolution -
> maybe this should be noted in the info file.

I agree.

> *: Eli's article has not yet arrived at my news server, but he emailed
> it to me as well as to djgpp AT delorie DOT com. I'm not sure how I'm supposed
> to reply/follow-up now. Should I post a new article to the newsgroup or
> should I simply hit the reply-button and Cc: it to the list?

Use Reply.  The News are full of delays like this: I routinely get
replies to articles I haven't yet seen posted, even when people post
news instead of writing to the email gateway.

- Raw text -