From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: 58966@debbugs.gnu.org
Subject: bug#58966: [Trunk] Xcode 14.1+ (and macOS 13.0+) deprecate sprintf()
Date: Thu, 03 Nov 2022 06:56:25 +0100 [thread overview]
Message-ID: <m2a658wph2.fsf@Mini.fritz.box> (raw)
In-Reply-To: <FAD4DF71-A76D-4933-8AF4-6AF389423D54@gmail.com> (Jacob Faibussowitsch's message of "Wed, 2 Nov 2022 09:56:41 -0400")
Jacob Faibussowitsch <jacob.fai@gmail.com> writes:
> Fresh build this morning produces many such warnings. I have attached
> config.log and make.log:
>
> buffer.c:1223:46: warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations]
> AUTO_STRING_WITH_LEN (lnumber, number, sprintf (number, "-%d", i));
> ^
Yeah, I've got 14.1 over night now, too, and I now see the same :-(.
From a hort look, just replacing sprintf variants with snprintf variants
won't be enough. Things like make_formatted_string would require
interface changes, for example.
I short, that looks to me like a ton of boring and potentially bug-prone
work.
What do the maintainers think about this?
next prev parent reply other threads:[~2022-11-03 5:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 13:56 bug#58966: [Trunk] Xcode 14.1+ (and macOS 13.0+) deprecate sprintf() Jacob Faibussowitsch
2022-11-03 5:56 ` Gerd Möllmann [this message]
2022-11-03 8:16 ` Eli Zaretskii
2022-11-03 9:00 ` Gerd Möllmann
2022-11-03 9:15 ` Eli Zaretskii
2022-11-03 9:36 ` Gerd Möllmann
2022-11-03 14:40 ` Jacob Faibussowitsch
2022-11-03 14:43 ` Gerd Möllmann
2022-11-03 14:48 ` Jacob Faibussowitsch
2022-11-03 15:22 ` Gerd Möllmann
2022-11-03 15:30 ` Jacob Faibussowitsch
2022-11-03 16:15 ` Gerd Möllmann
2022-11-03 16:19 ` Gerd Möllmann
2022-11-03 18:30 ` Paul Eggert
2022-11-04 21:07 ` Jacob Faibussowitsch
2022-11-05 3:12 ` Richard Stallman
2022-11-05 16:26 ` Stefan Kangas
2022-11-05 20:00 ` Paul Eggert
2022-11-07 7:46 ` Richard Stallman
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=m2a658wph2.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=58966@debbugs.gnu.org \
--cc=jacob.fai@gmail.com \
/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).