| Deutsch English Français Italiano |
|
<20250610142356.296@kylheku.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Kaz Kylheku <643-408-1753@kylheku.com> Newsgroups: comp.lang.c Subject: Re: encapsulating directory operations Date: Tue, 10 Jun 2025 21:34:23 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: <20250610142356.296@kylheku.com> References: <100h650$23r5l$1@dont-email.me> <20250520065158.709@kylheku.com> <100i2la$292le$1@dont-email.me> <87a5770xjw.fsf@nosuchdomain.example.com> <100j09o$2f04b$1@dont-email.me> <87tt5ezx9y.fsf@nosuchdomain.example.com> <100j4t3$2foah$1@dont-email.me> <87ldqqzfj0.fsf@nosuchdomain.example.com> <100kak8$2q0s6$1@dont-email.me> <87a575zvmb.fsf@nosuchdomain.example.com> <100o3sc$3ll6t$1@dont-email.me> <87bjrkxonr.fsf@nosuchdomain.example.com> <b7fb8fc41d43807641e673e1ca1d3baf69f5766f@i2pn2.org> <87iklrtcys.fsf@nosuchdomain.example.com> <864ixavbs4.fsf@linuxsc.com> <87plfys9a5.fsf@nosuchdomain.example.com> <86bjqvr3u5.fsf@linuxsc.com> <878qlzibco.fsf@nosuchdomain.example.com> Injection-Date: Tue, 10 Jun 2025 23:34:23 +0200 (CEST) Injection-Info: dont-email.me; posting-host="f379c01e6bf0906b3a1cd5c289b2d758"; logging-data="1589327"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/BeXQjARt2Sjs6yMjyWLv6cMiTZxza1KU=" User-Agent: slrn/pre1.0.4-9 (Linux) Cancel-Lock: sha1:59GKQmJvEn8L30fH8CVdNz7zWtQ= On 2025-06-10, Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote: > I find the reservation of potential errno macro names annoying. If the standard contained /no/ statements about what a given header file may reserve, then /any/ identifier whatsoever would be a potential clash. The errno reservation is kind of good because implementors often extend the set of errno constants. POSIX has a lot more of them than ISO C, and there are some vendor-specific ones. Anyway, you can safely ignore the reservation theatre, and just deal with clashes that happen, when they happen. (If you're lucky, that could just be never). Anyway, ISO C, POSIX and vendors have historically introduced new identifiers in spaces that were not previously declared as reserved. If you're ever hit by that, you will feel like a completel sucker if you've religiously adhered to namespaces from your end. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca