Path: ...!news.mixmin.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: Code guidelines Date: Wed, 4 Sep 2024 09:06:41 -0300 Organization: A noiseless patient Spider Lines: 17 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Wed, 04 Sep 2024 14:06:42 +0200 (CEST) Injection-Info: dont-email.me; posting-host="1faf17ca17b4b674f1c33ee4dfab027e"; logging-data="4008030"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18emQsp5XaBuhKUcH00yut3240tOsfV2Uc=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:ov6n83XjC0RZHe3aMA5fRjKxliA= In-Reply-To: Content-Language: en-US Bytes: 1767 On 04/09/2024 08:52, Thiago Adams wrote: .... > Perhaps the programmer knows something the compiler doesn’t? The idea of programmer overriding what compiler knows it not new. For instance, when casting from 'void*' to 'struct X' the programmer is overriding the type, that can be anything. But when overriding for instance, 'struct X*' to 'struct Y*' then the programming is overriding something the compiler already knows. The same concept of conflicting information could be applied to casts.?