public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/23432] incorrect printf output for integers with thousands separator and precision field larger than the number of digits (needing leading zeros)
Date: Mon, 06 Feb 2023 13:58:21 +0000	[thread overview]
Message-ID: <bug-23432-131-PiedKdJEwP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23432-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23432

--- Comment #8 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
Note that I was wrong in my initial bug report. For

  printf ("%'.17d\n", 123456789);

I said that it should output "000,000,123,456,789". Actually, there were 2
issues in the glibc 2.36- behavior: the missing thousands' grouping characters
with the leading zeros and the incorrect number of digits (15 instead of 17).
So the correct output should be "00,000,000,123,456,789".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-02-06 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23432-131@http.sourceware.org/bugzilla/>
2023-01-10 11:29 ` vincent-srcware at vinc17 dot net
2023-01-10 11:47 ` vincent-srcware at vinc17 dot net
2023-01-10 11:49 ` vincent-srcware at vinc17 dot net
2023-01-10 12:07 ` [Bug stdio/23432] incorrect printf output " vincent-srcware at vinc17 dot net
2023-01-10 12:23 ` [Bug stdio/23432] incorrect printf output for integers " vincent-srcware at vinc17 dot net
2023-01-10 12:32 ` vincent-srcware at vinc17 dot net
2023-01-17 12:15 ` schwab@linux-m68k.org
2023-01-17 12:51 ` vincent-srcware at vinc17 dot net
2023-01-17 13:32 ` schwab@linux-m68k.org
2023-02-02  1:22 ` vincent-srcware at vinc17 dot net
2023-02-06 13:58 ` vincent-srcware at vinc17 dot net [this message]
2023-02-06 15:21 ` cvs-commit at gcc dot gnu.org
2023-02-08  1:12 ` cvs-commit at gcc dot gnu.org

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=bug-23432-131-PiedKdJEwP@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).