Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #393217
| Path | csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
| Newsgroups | comp.lang.c |
| Subject | Re: "A diagram of C23 basic types" |
| Date | Tue, 06 May 2025 13:25:37 -0700 |
| Organization | None to speak of |
| Lines | 25 |
| Message-ID | <87bjs5fpvi.fsf@nosuchdomain.example.com> (permalink) |
| References | <87y0wjaysg.fsf@gmail.com> <vsj1m8$1f8h2$1@dont-email.me> <vsrqsh$qhuu$2@solani.org> <vt38i9$29prg$1@dont-email.me> <87h62ys4w5.fsf@nosuchdomain.example.com> <vt488v$35hh3$1@dont-email.me> <vt4n3d$3e8hi$1@dont-email.me> <86ecy2c5o4.fsf@linuxsc.com> <87mscprhhe.fsf@nosuchdomain.example.com> <20250409105549.000037dd@yahoo.com> <86semhawhs.fsf@linuxsc.com> <20250410115004.00005276@yahoo.com> <86ikn79mlq.fsf@linuxsc.com> <20250414125529.00000673@yahoo.com> <86a57p3kro.fsf@linuxsc.com> |
| MIME-Version | 1.0 |
| Content-Type | text/plain |
| Injection-Date | Tue, 06 May 2025 22:25:37 +0200 (CEST) |
| Injection-Info | dont-email.me; posting-host="200f1b2c855e9fa31fd1080bfdd034d6"; logging-data="3863271"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ZMPCmVuI+/ZFyVTvTGquO" |
| User-Agent | Gnus/5.13 (Gnus v5.13) |
| Cancel-Lock | sha1:DZPgR+SDKORaupcmapfe1yBxn5c= sha1:06CHGtZAKvoMMnrSJOgAJYUdYYg= |
| Xref | csiph.com comp.lang.c:393217 |
Show key headers only | View raw
Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
> Michael S <already5chosen@yahoo.com> writes:
>> On Mon, 14 Apr 2025 01:24:49 -0700
>> Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:
>>> about where they may or may not be used. Do you really have a
>>> problem avoiding identifiers defined in this or that library
>>> header, either for all headers or just those headers required for
>>> freestanding implementations?
>>
>> I don't know. In order to know I'd have to include all
>> standard headers into all of my C files
>
> Let me ask the question differently. Have you ever run into an
> actual problem due to inadvertent collision with a reserved
> identifier?
I'm not Michael, but I was once mildly inconvienced because I
defined a logging function called log(). The solution was trivial:
I changed the name.
[...]
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar
Re: "A diagram of C23 basic types" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-06 06:56 -0700
Re: "A diagram of C23 basic types" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-05-06 13:25 -0700
Re: "A diagram of C23 basic types" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-08 08:37 -0700
Re: "A diagram of C23 basic types" scott@slp53.sl.home (Scott Lurndal) - 2025-05-08 15:48 +0000
Re: "A diagram of C23 basic types" Kaz Kylheku <643-408-1753@kylheku.com> - 2025-05-08 16:32 +0000
Re: "A diagram of C23 basic types" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-08 22:53 -0700
Re: "A diagram of C23 basic types" antispam@fricas.org (Waldek Hebisch) - 2025-05-08 14:09 +0000
Re: "A diagram of C23 basic types" David Brown <david.brown@hesbynett.no> - 2025-05-08 16:52 +0200
Re: "A diagram of C23 basic types" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2025-05-08 08:49 -0700
csiph-web