Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: pointers Date: Mon, 24 Oct 2016 14:42:38 -0700 Organization: None to speak of Lines: 22 Message-ID: References: <18d7b7b9-ea72-49d3-9535-df13d560473c@googlegroups.com> <726d78eb-47b3-1b92-0203-e2f63bb740ae@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="dc97ebc10d9ee65592f107439c98c97d"; logging-data="18800"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19iwH2lHAtFxi14bq+1F2qZ" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:DfJWkJB7s7iKaySb9O0cBYi320M= sha1:Tr8tqMuMf6fG0cnReg6qbCXExg8= Xref: csiph.com comp.lang.c:95249 Tim Rentsch writes: > supercat@casperkitty.com writes: >> The Standard does [say] that no conforming extension should alter >> the effect of a strictly-conforming program, but many of the >> "Common Extensions" listed in the annex would do precisely that. > > That depends on how the extension is implemented, doesn't it? Or > are you saying that some of the listed common extensions would be > impossible to implement without changing some strictly conforming > programs? If so, which of the listed extensions fall into that > category? The "fortran" and "asm" keywords, if they're treated as keywords in all contexts, would clearly break strictly conforming programs that use them as identifiers (J.5.9, J.5.10). Likewise for predefined macro names using unreserved identifers (J.5.12). -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"