From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 12430@debbugs.gnu.org
Subject: bug#12430: Glitches caused by addition of psec to timers
Date: Thu, 13 Sep 2012 22:19:59 +0300 [thread overview]
Message-ID: <83obl9vig0.fsf@gnu.org> (raw)
In-Reply-To: <50522A90.2080208@cs.ucla.edu>
> Date: Thu, 13 Sep 2012 11:48:48 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: Stefan Monnier <monnier@iro.umontreal.ca>, 12430@debbugs.gnu.org
>
> On 09/13/2012 09:57 AM, Eli Zaretskii wrote:
> > Wouldn't it be better to leave timers at their previous size of 8, and
> > instead allow the usecs element be a floating-point number?
>
> That could introduce off-by-one errors due to rounding
> issues.
Not with correct programs that _want_ the sub-microsecond resolution.
> We could have the usecs element be a list, though.
> That is, (USECS PSECS) would stand for the sum of
> USECS microseconds and PSECS picoseconds, whereas
> a plain USECS would be treated as a microseconds count,
> as before.
Yes, that's also a possibility, although it is less compatible (e.g.,
fails the 'numberp' test). Any backward-compatible structure is
better than an incompatible one. If 'timerp' just checks the number
of elements in the array, so could some code out there.
next prev parent reply other threads:[~2012-09-13 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 6:04 bug#12430: Glitches caused by addition of psec to timers Paul Eggert
2012-09-13 12:49 ` Stefan Monnier
2012-09-13 16:26 ` Paul Eggert
2012-09-13 16:57 ` Eli Zaretskii
2012-09-13 18:48 ` Paul Eggert
2012-09-13 19:19 ` Eli Zaretskii [this message]
2012-09-13 19:37 ` Paul Eggert
2012-09-13 20:11 ` Glenn Morris
2012-09-14 6:32 ` Eli Zaretskii
2012-09-13 21:35 ` Stefan Monnier
2012-09-14 6:32 ` Eli Zaretskii
2012-09-14 13:18 ` Stefan Monnier
2012-09-14 13:44 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83obl9vig0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12430@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).