Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: "A diagram of C23 basic types" Date: Sun, 06 Apr 2025 19:33:55 -0700 Organization: None to speak of Lines: 19 Message-ID: <87ikngd7jg.fsf@nosuchdomain.example.com> References: <87y0wjaysg.fsf@gmail.com> <20250402113624.693@kylheku.com> <86o6xdhorr.fsf@linuxsc.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Mon, 07 Apr 2025 04:34:03 +0200 (CEST) Injection-Info: dont-email.me; posting-host="2714e7df686d80d73a1feebaa5e76a7a"; logging-data="2643523"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+7fe7svgDfbc84hjVFNm0K" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:PQSW14AHEio5q/zJh1PyRRJj9TM= sha1:DFMkqh+5boY+NM8JUaKQnueBqps= Bytes: 2007 antispam@fricas.org (Waldek Hebisch) writes: > 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. Convenience and existing practice. Sure, an implementation of could provide a declaration of memcpy() without making size_t visible, but what would be the point? [...] -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com void Void(void) { Void(); } /* The recursive call of the void */