From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Use of %td in printf
Date: Wed, 03 Jul 2019 11:31:46 +0300 [thread overview]
Message-ID: <8336jncydp.fsf@gnu.org> (raw)
In-Reply-To: <3cacec12-2b5b-3145-1c30-fd570765de40@cs.ucla.edu> (message from Paul Eggert on Wed, 3 Jul 2019 01:04:33 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 3 Jul 2019 01:04:33 -0700
>
> Eli Zaretskii wrote:
> > AFAIR, we require a C99 compiler, but not a C99 C library.
>
> That was a while ago. These days it's safe to assume %td and Emacs has been
> doing so for some time without any problems.
Thanks, I just wanted to be sure. I don't really know of any platform
where this could cause problems.
> I should mention that the situation is more complicated than "we require a C99
> compiler". Emacs does not require full support for C99, either in the compiler
> or the library. (If it did, we couldn't use Microsoft's C compiler, which does
> not support all of C99.)
We don't support building with the Microsoft compiler for quite some
time now. The MS-Windows port is built using GCC, not MSVC.
> While we're on the topic, one of these days I was thinking of removing
> printmax_t and related types and macros from src/lisp.h, as %jd is considerably
> simpler and should be universal by now. Even when I added that stuff back in
> 2011 the concern about portability to old C libraries lacking %jd support was
> mostly theoretical; I think the last holdout was Solaris 8, which Oracle stopped
> supporting in 2012. Nowadays those pre-C99 libraries are museum pieces and we
> can drop the printmax_t hacks.
If all the platforms we care about support that, fine.
prev parent reply other threads:[~2019-07-03 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 6:03 Use of %td in printf Eli Zaretskii
2019-07-03 7:33 ` Paul Eggert
2019-07-03 7:44 ` Eli Zaretskii
2019-07-03 8:04 ` Paul Eggert
2019-07-03 8:31 ` Eli Zaretskii [this message]
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=8336jncydp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.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.
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).