Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: New features added into C23 standard Date: Mon, 15 Aug 2022 23:24:39 -0700 Organization: A noiseless patient Spider Lines: 12 Message-ID: <86tu6cu2mw.fsf@linuxsc.com> References: <3093c98e-d014-47e4-bcf3-3f108d7c2c03n@googlegroups.com> <87mtcwzwt9.fsf@nosuchdomain.example.com> <88293f89-5f19-4fb3-844b-20e3a063b65cn@googlegroups.com> <87sfmh6xrw.fsf@bsb.me.uk> <87mtcp6srv.fsf@bsb.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader01.eternal-september.org; posting-host="327aa8f3763fd82bcbb1f30d2282ba71"; logging-data="4639"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1812rLwtfxem2wh4jn3PjO46JgQlX4J2gQ=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:xw8WLzhJ7uUapiazf53tiX8plmM= sha1:R0zOP+OQTacAXzQoZqYZOKvTMJk= Xref: csiph.com comp.lang.c:167037 Richard Damon writes: [...] > The key point is that *IF* the implementation defines how to > access a specific location of memory, and you use that method, > then the implementation must honor its definition. AFAIAA, the C standard does not require that implementations carry out their documented extensions correctly. We might like it to be so, but I don't see anything in the C standard that requires it.