Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: encapsulating directory operations Date: Fri, 23 May 2025 22:22:58 -0700 Organization: A noiseless patient Spider Lines: 41 Message-ID: <86zff2twel.fsf@linuxsc.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> <87iklrtcys.fsf@nosuchdomain.example.com> <20250523132019.763@kylheku.com> <100qm76$7shk$2@dont-email.me> <20250523140729.787@kylheku.com> <100qru0$9mjb$2@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Date: Sat, 24 May 2025 07:22:59 +0200 (CEST) Injection-Info: dont-email.me; posting-host="34797294a24bb7c5bba48f4b74fba193"; logging-data="576248"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX183POfEHZ1OOahckI3ems638i5wzpFXQMc=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:W0WelGlZoflwCG1AlTrBrsd5IoA= sha1:E8RTFBprWFT6nHIpNECQC3Thnns= Xref: csiph.com comp.lang.c:393583 Richard Heathfield writes: > On 23/05/2025 22:10, Kaz Kylheku wrote: > >> On 2025-05-23, Richard Heathfield wrote: >> >>> On 23/05/2025 21:27, Kaz Kylheku wrote: >>> >>>> On 2025-05-23, Keith Thompson wrote: >>> >>> >>> >>>>> (Identifiers starting with E followed by either a digit or an uppercase >>>>> letter are reserved; they could be defined as macros in .) >>>> >>>> But C99 introduced, for instance "double round(double);" >>> >>> I am tempted to ask 'who cares?' but I will sit on my hands and >>> be good. >> >> That's essentially what I'm saying. > > But we refuse to care for different reasons, it seems. > >> Who cares about the silly reserved >> name spaces that provide nothing you can rely on to thwart future name >> clashes. > > And who cares about future instability if C90 remains just as stable > as ever it was? (If care there is, it's caring that implementors > continue to include C90 implementations in their repertoire.) There's a catch though to that "future instability" matter. Some sets of names described in library headers, such as the ESCAPE example of this thread, are reserved and allowed to change even in a conforming C90 implementation. A seemingly innocuous line of code such as int towel; could run afoul of this rule, even in a strictly C90 environment.