Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: "A diagram of C23 basic types"
Date: Wed, 02 Apr 2025 20:53:49 -0700
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <86wmc1hpde.fsf@linuxsc.com>
References: <87y0wjaysg.fsf@gmail.com> <vsinf4$17d6t$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Thu, 03 Apr 2025 05:53:51 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="5fae27e4725ec0f03e8fd915a6650b3a";
	logging-data="3846998"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+fs8ghbrjJ0JtkSAQsvpcpHyNKMfvvvSw="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:Zh1L2D4XNlWrIuCn4RT0oMAKMCE=
	sha1:Nf5EO7VVOH2gA4AIB2tIMpCLtQA=

Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:

[...]

> I see the 'bool' but recently seen mentioned some '_Bool' type.
> The latter was probably chosen in that special syntax to avoid
> conflicts during "C" language evolution?
> How do regular "C" programmers handle that multitude of boolean
> types;  ranging from use of 'int', over own "bool" types, then
> '_Bool', and now 'bool'?  Since it's a very basic type it looks
> like you need hard transitions in evolution of your "C" code?

I use a typedef, in order to isolate code from changes in the C
standard, and to facilitate moving code from one compilation
environment to another.  As much as I can I try to write code
that is both platform- and standard-version- independent (within
limits, obviously, but usually code can be written so that there
will be complaints at compile time if the relevant limits are not
observed).