From: <rsbecker@nexbridge.com>
To: "'Elijah Newren'" <newren@gmail.com>,
"'Phillip Wood'" <phillip.wood@dunelm.org.uk>
Cc: git@vger.kernel.org, "'René Scharfe'" <l.s.r@web.de>,
"'Brian M . Carlson'" <sandals@crustytoothpaste.net>,
"'Eric Sunshine'" <sunshine@sunshineco.com>
Subject: RE: [PATCH v2 0/3] C99: declare bool experiment a success
Date: Tue, 15 Jul 2025 14:23:14 -0400 [thread overview]
Message-ID: <000001dbf5b5$8b316f00$a1944d00$@nexbridge.com> (raw)
In-Reply-To: <CABPp-BHoTxT1UQtgy2bH=mc1re_LPngKX-50GPh_wbtMMZZpyQ@mail.gmail.com>
On July 15, 2025 1:19 PM Elijah Newren wrote:
>On Tue, Jul 15, 2025 at 6:53 AM Phillip Wood <phillip.wood123@gmail.com>
>wrote:
>>
>> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>>
>> We've had a test balloon for C99's bool type since 8277dbe987
>> (git-compat-util: convert skip_{prefix,suffix}{,_mem} to bool,
>> 2023-12-16). As it has been over 18 months since this was added and
>> there have been no complaints let's declare it a success and convert
>> the return type our other string predicates to match.
>>
>> Thank you to everyone who commented on V1, the only change here is to
>> fix the typos in the commit message for patch 2.
>>
>> Base-Commit: a30f80fde927d70950b3b4d1820813480968fb0d
>> Published-As:
>> https://github.com/phillipwood/git/releases/tag/pw%2Fuse-c99-bool%2Fv2
>> View-Changes-At:
>> https://github.com/phillipwood/git/compare/a30f80fde...669687147
>> Fetch-It-Via: git fetch https://github.com/phillipwood/git
>> pw/use-c99-bool/v2
>>
>>
>> Phillip Wood (3):
>> CodingGuildlines: allow the use of bool
>> git-compat-util: convert string predicates to return bool
>> strbuf: convert predicates to return bool
>>
>> Documentation/CodingGuidelines | 3 +++
>> git-compat-util.h | 12 ++++++------
>> strbuf.c | 28 ++++++++++++++--------------
>> strbuf.h | 12 ++++++------
>> 4 files changed, 29 insertions(+), 26 deletions(-)
>>
>> Range-diff against v1:
>> 1: 352f80c49b7 = 1: 352f80c49b7 CodingGuildlines: allow the use of
>> bool
>> 2: a0f9182aa20 ! 2: 0b2402e11cc git-compat-util: convert string predicates to
>return bool
>> @@ Commit message
>> git-compat-util: convert string predicates to return bool
>>
>> Since 8277dbe987 (git-compat-util: convert skip_{prefix,suffix}{,_mem}
>> - to bool, 2023-12-16) a number of our sting predicates have been
>> - returning bool instead of int. Now we've declared that experiment
>> - a success lets convert the return type the case independent
>> + to bool, 2023-12-16) a number of our string predicates have been
>> + returning bool instead of int. Now that we've declared that experiment
>> + a success, let's convert the return type of the case-independent
>> skip_iprefix() and skip_iprefix_mem() functions to match the return
>> - type of their case dependent equivalents. Returning bool instead of
>> + type of their case-dependent equivalents. Returning bool instead of
>> int makes it clear that these functions are predicates.
>>
>> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
>> 3: 7eaf8042061 = 3: 66968714739 strbuf: convert predicates to return
>> bool
bool is not standard in all c99 implementations. I have to #include <stdbool.h> in order to
use this type. Please make sure there is a mechanism for that.
next prev parent reply other threads:[~2025-07-15 18:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:26 [PATCH 0/3] C99: declare bool experiment a success Phillip Wood
2025-07-14 13:27 ` [PATCH 1/3] CodingGuildlines: allow the use of bool Phillip Wood
2025-07-14 16:37 ` Junio C Hamano
2025-07-14 13:27 ` [PATCH 2/3] git-compat-util: convert string predicates to return bool Phillip Wood
2025-07-14 16:46 ` Eric Sunshine
2025-07-14 17:20 ` Elijah Newren
2025-07-14 21:14 ` brian m. carlson
2025-07-15 9:36 ` Phillip Wood
2025-07-14 13:27 ` [PATCH 3/3] strbuf: convert " Phillip Wood
2025-07-15 13:52 ` [PATCH v2 0/3] C99: declare bool experiment a success Phillip Wood
2025-07-15 13:52 ` [PATCH v2 1/3] CodingGuildlines: allow the use of bool Phillip Wood
2025-07-16 4:38 ` Jeff King
2025-07-16 4:46 ` Jeff King
2025-07-16 5:06 ` Elijah Newren
2025-07-15 13:52 ` [PATCH v2 2/3] git-compat-util: convert string predicates to return bool Phillip Wood
2025-07-15 13:52 ` [PATCH v2 3/3] strbuf: convert " Phillip Wood
2025-07-15 17:19 ` [PATCH v2 0/3] C99: declare bool experiment a success Elijah Newren
2025-07-15 18:23 ` rsbecker [this message]
2025-07-15 19:35 ` Elijah Newren
2025-07-15 20:47 ` rsbecker
2025-07-15 21:06 ` Junio C Hamano
2025-07-15 18:53 ` Junio C Hamano
2025-07-15 21:48 ` brian m. carlson
2025-07-15 22:09 ` Junio C Hamano
2025-07-16 9:38 ` [PATCH v3 " Phillip Wood
2025-07-16 9:38 ` [PATCH v3 1/3] CodingGuidelines: allow the use of bool Phillip Wood
2025-07-16 9:38 ` [PATCH v3 2/3] git-compat-util: convert string predicates to return bool Phillip Wood
2025-07-16 10:26 ` Karthik Nayak
2025-07-16 9:38 ` [PATCH v3 3/3] strbuf: convert " Phillip Wood
2025-07-16 10:28 ` Karthik Nayak
2025-07-16 10:29 ` [PATCH v3 0/3] C99: declare bool experiment a success Karthik Nayak
2025-07-17 15:21 ` Phillip Wood
2025-07-22 8:09 ` Karthik Nayak
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='000001dbf5b5$8b316f00$a1944d00$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=newren@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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.
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 NNTP newsgroup(s).