From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 32902@debbugs.gnu.org
Subject: bug#32902: Add support for (TIMESTAMP . RESOLUTION) Lisp timestamps
Date: Sun, 07 Oct 2018 20:55:54 +0300 [thread overview]
Message-ID: <8336th1w0l.fsf@gnu.org> (raw)
In-Reply-To: <bc4d857d-daf7-562f-ceb9-27f672ebc9ee@cs.ucla.edu> (message from Paul Eggert on Sat, 6 Oct 2018 23:32:00 -0700)
> Cc: 32902-done@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 6 Oct 2018 23:32:00 -0700
>
> Eli Zaretskii wrote:
> > OK, but can we call the new file something like timefns.c?
>
> Sure, that's easy enough. I revamped the patches to do that and installed them
> into master. Closing the bug report.
Thanks.
I saw a compilation problem with mingw.org's MinGW:
timefns.c: In function 'lisp_to_timespec':
timefns.c:899:21: warning: passing argument 2 of 'mpz_time' from incompatible pointer type [-Wincompatible-pointer-types]
if (mpz_time (*q, &result.tv_sec))
^
timefns.c:828:1: note: expected 'time_t * {aka long int *}' but argument is of type '__time64_t * {aka long long int *}'
mpz_time (mpz_t const z, time_t *t)
^~~~~~~~
I fixed it, but please take a look, perhaps there's a better fix for
this situation.
next prev parent reply other threads:[~2018-10-07 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 1:00 bug#32902: Add support for (TIMESTAMP . RESOLUTION) Lisp timestamps Paul Eggert
2018-10-02 3:04 ` Eli Zaretskii
2018-10-03 18:45 ` Paul Eggert
2018-10-04 16:08 ` Eli Zaretskii
2018-10-07 6:32 ` Paul Eggert
2018-10-07 17:55 ` Eli Zaretskii [this message]
2018-10-07 20:05 ` Paul Eggert
2018-10-08 2:44 ` Eli Zaretskii
2018-10-08 5:18 ` Paul Eggert
2018-10-09 15:09 ` Eli Zaretskii
[not found] ` <3f0bcf06-83f2-a0e9-c9ab-b06d65417afe@cs.ucla.edu>
2018-10-10 3:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8336th1w0l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32902@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.