From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: get-internal-real-time using times()
Date: Fri, 12 Sep 2003 14:25:29 -0500 [thread overview]
Message-ID: <87ekylu7va.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87d6ein7fl.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 03 Sep 2003 08:37:18 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> * stime.c (scm_get_internal_real_time, scm_your_base,
> scm_init_stime): Use times() when available, for a genuine
> real-time (unaffected by stime system time changes).
>
> The name "real-time" suggests to me something independent of the
> system date/time. And since the return is clock ticks, times() would
> seem natural. Unless there's a particular reason it isn't already so.
Presuming I understand what you're doing here (from a brief look), we
might want to be careful. 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, 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 did
I misunderstand?
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
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 19:25 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 [this message]
2003-09-12 23:46 ` Kevin Ryde
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=87ekylu7va.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
/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).