From: Grant Edwards <grant.b.edwards@gmail.com>
To: newlib@sourceware.org
Subject: Re: [EXTERNAL]: Re: Why int32_t is long int on 32 Bit Intel?
Date: Fri, 28 Jul 2023 18:05:38 -0000 (UTC) [thread overview]
Message-ID: <ua101h$13q5$1@ciao.gmane.io> (raw)
In-Reply-To: <5F615A8B-DB01-4824-9486-4AD146D6B991@damon-family.org>
On 2023-07-28, Richard Damon <Richard@damon-family.org> wrote:
> Actually, it is showing you are using the “wrong” format. If you are
> printing an int32_t, you should be using the format out of
> inttypes.h to be correct, even if it is “ugly”.
Huh. I never knew about inttype.h until now and always wondered about
the "official" way to deal with this problem. [IMO, it definitely is
ugly.]
I tended to use the %ld with a (long) cast solution -- which doesn't
generate any extra code and is easy to read, but it still didn't seem
"right".
--
Grant
next prev parent reply other threads:[~2023-07-28 18:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:55 panda.trooper
2023-07-27 23:13 ` Brian Inglis
2023-07-28 8:06 ` panda.trooper
2023-07-28 13:23 ` Anders Montonen
2023-07-28 14:15 ` Joel Sherrill
2023-07-28 15:49 ` [EXTERNAL]: " Mike Burgess
2023-07-28 16:11 ` Stefan Tauner
2023-07-28 16:26 ` Mike Burgess
2023-07-28 17:06 ` Richard Damon
2023-07-28 18:05 ` Grant Edwards [this message]
2023-07-28 18:27 ` panda.trooper
2023-07-28 20:23 ` Jon Beniston
2023-07-28 21:42 ` panda.trooper
2023-07-28 21:53 ` Jon Beniston
2023-07-29 12:47 ` Trampas Stern
2023-07-29 13:19 ` Stefan Tauner
2023-07-29 21:21 ` Grant Edwards
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='ua101h$13q5$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=newlib@sourceware.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).