From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Use gnulib c-ctype module, not <ctype.h>
Date: Tue, 09 Sep 2025 12:55:27 -0600 [thread overview]
Message-ID: <87ikhrpiao.fsf@tromey.com> (raw)
In-Reply-To: <3208ce09-e47c-4355-898e-321891a26558@simark.ca> (Simon Marchi's message of "Tue, 9 Sep 2025 14:01:42 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>> Just as a reminder to everyone, gdb should generally use these new
>> "c-ctype" wrapper functions and not <ctype.h>.
>>
>> One idea I had for enforcement was to write a new pre-commit script that
>> looked for includes of ctype.h or safe-ctype.h. WDYT?
Simon> 1. Should all includes of ctype.h and safe-ctype.h be removed from GDB
Simon> right now, in any case?
Yeah, this series did that.
Simon> 2. Is ctype.h available transitively anyway? If so, we could add a
Simon> call to a ctype.h function without adding an include, so the script
Simon> wouldn't catch it.
That's true, it's available sometimes depending on which libstdc++
headers are included.
Tom
next prev parent reply other threads:[~2025-09-09 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 13:13 Tom Tromey
2025-08-06 13:13 ` [PATCH 1/3] Import the c-ctype module from gnulib Tom Tromey
2025-08-06 13:13 ` [PATCH 2/3] Use c-ctype.h (not safe-ctype.h) in gdb Tom Tromey
2025-08-06 13:13 ` [PATCH 3/3] Use gnulib c-ctype module " Tom Tromey
2025-08-06 19:46 ` [PATCH 0/3] Use gnulib c-ctype module, not <ctype.h> Simon Marchi
2025-08-07 20:39 ` Tom Tromey
2025-08-20 17:14 ` Simon Marchi
2025-09-09 17:53 ` Tom Tromey
2025-09-09 18:01 ` Simon Marchi
2025-09-09 18:55 ` Tom Tromey [this message]
2025-10-14 13:00 ` Guinevere Larsen
2025-10-14 19:19 ` Tom Tromey
2025-10-16 15:30 ` Tom Tromey
2025-10-16 21:50 ` Luis
2025-10-21 12:59 ` Tom Tromey
2025-10-21 17:37 ` Simon Marchi
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=87ikhrpiao.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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