Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: The case AGAINST C Date: Fri, 04 May 2018 10:54:45 -0700 Organization: None to speak of Lines: 28 Message-ID: References: <7371a825-33bc-4723-9ed7-18f23f55e76a@googlegroups.com> <66d56564-0b72-44b5-aba9-783e62eeed97@googlegroups.com> <0wXGC.68476$ny5.58646@fx17.am4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="067bb2bcf7afe0ff6fbb1a4a3dfb8c90"; logging-data="10415"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Z5rytsg71CLrO5uiHhv9/" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:J3ryKne2j6yhDeys3ZC8lHySqqk= sha1:rX/AB7l+MLNlcRKS4tTBy6dJYCA= Xref: csiph.com comp.lang.c:130200 bartc writes: > On 04/05/2018 17:05, Keith Thompson wrote: >> bartc writes: >> [...] >>> C's #include is nothing to do with modules, nor headers for that matter, >>> and it doesn't understand anything about either. >> >> #include has nothing to do with headers? >> >> Perhaps you have a different meaning for the word "header" than the rest >> of us do. > > I said that #include doesn't understand headers. Yes, you also said that. What you actually wrote is still quoted at the top of this article. You wrote that "C's #include is nothing to do with ... headers". That's clearly untrue. Perhaps whatever it was you meant to say is true, but I don't know what that is. -- 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"