Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Thiago Adams Newsgroups: comp.lang.c Subject: Re: how cast works? Date: Sat, 10 Aug 2024 20:01:36 -0300 Organization: A noiseless patient Spider Lines: 16 Message-ID: References: <87ttfu94yv.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sun, 11 Aug 2024 01:01:38 +0200 (CEST) Injection-Info: dont-email.me; posting-host="5178e0c40238d6cd6e3cb7269b7f3c31"; logging-data="1007543"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19/fFVdljZjqPksvOY8ISG8gYzQAikFu1k=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:L528cE0565wUkJLtuvCaUdsFiQs= Content-Language: en-GB In-Reply-To: Bytes: 1896 Em 8/10/2024 1:14 PM, Bart escreveu: >> >> Bart, Does your compiler support the `bool` type, where the value is >> always either 1 or 0? > > There is a bool type, but it is treated like unsigned char, so is > non-conforming. I do the same in my compiler , when I transpile from C99 to C89. I was thinking how to make it conforming. For instance on each write. bool b = 123; -> unsigned char b = !!(123); The problem this does not fix unions, writing on int and reading from char.