Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: James Kuyper Newsgroups: comp.lang.c Subject: Re: "A diagram of C23 basic types" Date: Mon, 7 Apr 2025 14:35:52 -0400 Organization: A noiseless patient Spider Lines: 18 Message-ID: References: <87y0wjaysg.fsf@gmail.com> <20250402113624.693@kylheku.com> <86o6xdhorr.fsf@linuxsc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Injection-Date: Mon, 07 Apr 2025 20:36:11 +0200 (CEST) Injection-Info: dont-email.me; posting-host="7ff09bee0ae2c8930133536c6909c328"; logging-data="441365"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+NTG+pCzmPYuhdtpZwsUAk2HgQ8GcoPRc=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:Cguh+VZ3o8ZxXKYklKuNZlStw0o= Content-Language: en-US In-Reply-To: Bytes: 2199 On 4/3/25 18:00, Waldek Hebisch wrote: > Tim Rentsch wrote: .... >> Not always practical. A good example is the type size_t. If a >> function takes an argument of type size_t, then the symbol size_t >> should be defined, no matter which header the function is being >> declared in. > > Why? One can use a type without a name for such type. How would you declare a pointer to a function type such that it is compatible with such a function's type? When a variable is needed to store a value that would be passed as the size_t argument to such a function, I would (in the absence of any specific reason to do otherwise) want to declare that object to have the type size_t. Why should I have to #include a different header just because I want to do these things?