From: Kevin Ryde <user42@zip.com.au>
Subject: Re: get-internal-real-time using times()
Date: Sat, 13 Sep 2003 09:46:29 +1000 [thread overview]
Message-ID: <87wucdin8q.fsf@zip.com.au> (raw)
In-Reply-To: <87ekylu7va.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Fri, 12 Sep 2003 14:25:29 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
>
> If the old semantics of
> get-internal-real-time relied on ftime, then people may have written
> code that depends on the fact that get-internal-real-time has been
> returning wall-clock time,
I guess that's possible, though I might think it unlikely anyone who
understands the distinction would assume a function called `real-time'
in fact gives wall time.
> and in fact, when contrasted to
> get-internal-run-time's description (and given familiarity with the
> "times" distinctions), that might be a reasonable presumption.
Or one could assume that since -run-time is unaffected then -real-time
is also unaffected.
If the system time doesn't change too often then I guess there's not
much difference. But I can't help thinking that it's not good for a
function called real-time to go backwards or suddenly jump forwards.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-09-12 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 22:37 get-internal-real-time using times() Kevin Ryde
2003-09-12 19:25 ` Rob Browning
2003-09-12 23:46 ` Kevin Ryde [this message]
2003-09-13 2:51 ` Rob Browning
2003-09-15 22:47 ` Kevin Ryde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wucdin8q.fsf@zip.com.au \
--to=user42@zip.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).